Behaviour change in 0.19.0 #1569
-
BodyFirst of all, thanks for the amazing software! Steps to reproduce:
Expected result: the window would just open on workspace 3 (behaviour in 0.18.5) before.mp4Actual result: after.mp4Additional info$ aerospace -v
aerospace CLI client version: 0.19.1-Beta bcdf20b8388b1eecd97b7ce97f64c0759be310c8
AeroSpace.app server version: 0.19.1-Beta bcdf20b8388b1eecd97b7ce97f64c0759be310c8[[on-window-detected]]
if.app-id = 'com.googlecode.iterm2'
run = ['layout floating'] # The callback itself
check-further-callbacks = false |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
Can you please capture iTerm quake window accessibility debug info by using |
Beta Was this translation helpful? Give feedback.
-
|
I have this same problem! Here's my own video demonstrating the problem. Could it be the same root cause as this issue? NoMachine - Aerospace forcefully jumps back to previous workspace #1546 I see the solution implemented there was specific to nomachine's bundleId ( |
Beta Was this translation helpful? Give feedback.
-
|
I don't know what exactly changed between 0.18.5 and 0.19.1. And the log above isn't helpful, unfortunately, because it says that the window is detected in the similar way: 81a82,83
> "Aero.AxUiElementWindowType" : "window",
> "Aero.AxUiElementWindowType_isDialogHeuristic" : false,
83,84c85
< "Aero.isDialogHeuristic" : false,
< "Aero.isWindowHeuristic" : true,But I think I figured how hotkey windows could be recognized. Tracking issue: #1813 |
Beta Was this translation helpful? Give feedback.
I don't know what exactly changed between 0.18.5 and 0.19.1.
And the log above isn't helpful, unfortunately, because it says that the window is detected in the similar way:
But I think I figured how hotkey windows could be recognized. Tracking issue: #1813