-
-
Notifications
You must be signed in to change notification settings - Fork 643
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
Unintuitive navigation controls #1220
Labels
bug
Something isn't working
Comments
This bothered me as well, but can be fixed very easily: FelixKratz@15adc07 |
Implemented better detection logic on master. |
koekeishiya
added
the
addressed on master; not released
Fixed upstream, but not yet released
label
Apr 3, 2022
koekeishiya
added a commit
that referenced
this issue
Apr 3, 2022
koekeishiya
added a commit
that referenced
this issue
Apr 21, 2022
koekeishiya
removed
the
addressed on master; not released
Fixed upstream, but not yet released
label
May 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #1210
I first posted about this in Discussions along with some ideas for improving the system, but I've since become convinced it's an actual issue that needs fixing.
Here's a short screen recording illustrating the problem in an easily reproducible situation.
(The only shortcuts used are
window --focus west
andwindow --focus east
represented by the ← → arrows in the windows.)yabai-nav2.mp4
Stage 1:
Focusing → then ← brings me to a different window than I started on. Not a big deal since the situation is 'ambiguous' due to the two possible targets. If Yabai resolves this consistently (it does not) I could get used to this.
Stage 2:
Everything works as expected
Stage 3:
A small change from stage 2, yet now ← brings me to the window
?
for seemingly no reason. This is the biggest issue which I run into on a daily basis, and it makes directional focusing/manipulation of windows hard to understand.The linked discussion goes into a little more detail on possible solutions. I'd be willing to help contribute a fix, but unsure if others are facing the same issues.
The text was updated successfully, but these errors were encountered: