You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I move a window to a space on a different display, where the target space is in float layout, the window ends upp off screen. This happens both when I trigger it directly using e.g. yabai -m window --space 1, and when the window is moved by a rule like yabai -m rule --add app=Finder space=1.
If I activate Mission Control I can see that the window belongs to the target space, as the animation slides it in place there from the location of the original display. If I click it to activate it, it moves back off screen in the direction of the original display as Mission Control exits.
If I select Window → Zoom in the menu of the application it will move back on screen on the currently visible space on the original display. If I instead place it using yabai -m window --grid it is correctly placed on the target space.
Is this expected behaviour? I'm really just telling yabai to move the window to the new space, not to move it to some new coordinates. But I would have expected yabai to locate it at least at the same relative coordinates as on the original display. And I believe it has worked before.
I'm running with SIP enabled so without the scripting addition. I'm on Sonoma 14.7, so this shouldn't be the same issue as with Sequoia.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When I move a window to a space on a different display, where the target space is in float layout, the window ends upp off screen. This happens both when I trigger it directly using e.g.
yabai -m window --space 1, and when the window is moved by a rule likeyabai -m rule --add app=Finder space=1.If I activate Mission Control I can see that the window belongs to the target space, as the animation slides it in place there from the location of the original display. If I click it to activate it, it moves back off screen in the direction of the original display as Mission Control exits.
If I select Window → Zoom in the menu of the application it will move back on screen on the currently visible space on the original display. If I instead place it using
yabai -m window --gridit is correctly placed on the target space.Is this expected behaviour? I'm really just telling yabai to move the window to the new space, not to move it to some new coordinates. But I would have expected yabai to locate it at least at the same relative coordinates as on the original display. And I believe it has worked before.
I'm running with SIP enabled so without the scripting addition. I'm on Sonoma 14.7, so this shouldn't be the same issue as with Sequoia.
Beta Was this translation helpful? Give feedback.
All reactions