Skip to content
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

Cardinal movement arguments for swap/warp consider unmanaged windows #561

Closed
eramdam opened this issue Jun 8, 2020 · 5 comments
Closed

Comments

@eramdam
Copy link

eramdam commented Jun 8, 2020

Ever since 3.0.0 I've noticed a weird behaviour. It seems as if unmanaged windows are being considered for swap/wrap actions, thus blocking said action.

I've recorded the behavior in the video below https://www.dropbox.com/s/ztzeufpc7ko5urv/yabai-wrap.mp4?dl=0

After running a git bisect on the repo, I've ended up on a763f98 which implemented the euclidian distance logic to find a target window, so I don't know if the issue is really that unmanaged windows are being wrongfully considered or if the distance logic needs to be tweaked 😅

My gut feeling says that unmanaged windows should be ignored by warp/swap actions because those actions aren't really useful outside of the bsp layout but I may be missing some other perspective.

@eramdam
Copy link
Author

eramdam commented Jun 8, 2020

I've noticed that this might be related to #531 (comment)

I also noticed that the next, prev, last and first arguments aren't affected by this since they consider only the managed windows. So I guess the fix would be to harmonize the cardinal direction arguments for warp/swap so they would only consider managed windows?

@eramdam eramdam changed the title Unmanaged window wrongfully considered when warping/swapping windows Cardinal movement arguments for swap/warp consider unmanaged windows Jun 8, 2020
@koekeishiya
Copy link
Owner

koekeishiya commented Jun 8, 2020 via email

@eramdam
Copy link
Author

eramdam commented Jun 8, 2020

Huh, I guess I assumed that because I get an error saying
the selected window is not managed.

When running the command directly. So I guess it tries to find a target window and then bails out if it's unmanaged rather than continue trying until it finds a managed window*?

*option which i assume could be dangerous because you don't want to end up in an infinite loop 😅

@koekeishiya
Copy link
Owner

koekeishiya commented Jun 8, 2020 via email

@koekeishiya
Copy link
Owner

This is a bug indeed, closing this in favour of #562

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants