-
-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Window focus wraps around, moving west from leftmost window on 90° rotated display #1511
Comments
I am not experiencing this any longer with yabai-v5.0.2. Edit: That is using the following skhdrc keymaps which again work as expected
|
Either this has returned or I misunderstood the details of what was failing the last time around, cause you will not experience the following if you only have one window on each of the displays. Here's some more details: With displays
With displays
I would expect the movement to go directly from This is yabai-v5.0.4 |
I experienced a similar issue, and I hope my workaround can help you as well. Upon briefly examining the code, I suspected that the slight overlapping of windows was triggering a bug related to window focus management. By introducing a small gap between the windows, my specific issue was resolved. I set my window gap to 5:
|
I was unable to reproduce this specific issue, but I have fixed an off-by-one issue on master that caused a similar issue: #1463 (comment) |
Probably fixed in v5.0.5. Feel free to reopen if you can reproduce the issue in the new version. |
Works like a charm, thanks! |
With a dual screen setup like this
The following command, executed from the rightmost window in
a
, exits with code 1..making it a great candidate for chaining, e.g. like this
yabai -m window --focus east || yabai -m display --focus east
to move focus to displayb
However, the opposite, ran from the leftmost window on the 90° rotated display
b
exits with code 0..and instead "wraps" the focus to the last window on display
b
.Edit:
This is on
yabai-v5.0.1
The text was updated successfully, but these errors were encountered: