-
Notifications
You must be signed in to change notification settings - Fork 15
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
tree: focus float nodes when switching workspaces #335
tree: focus float nodes when switching workspaces #335
Conversation
This looks good in general. |
a81e2d6
to
e1bbbb4
Compare
One thing I'm not sure about is if floating containers should be prioritized over tiling ones. Currently it's the floating containers but that feels motivated by the fact that there doesn't yet seem to be a way to focus them with the keyboard. |
I had only reviewed from my phone so far and hadn't caught that your change prioritizes floating windows over tiled ones. I'd prefer to only focus floating windows if all of the existing logic fails. As you say, the inability to navigate such windows with the keyboard alone exists independently workspace focus behavior. |
e1bbbb4
to
834eedc
Compare
Sounds good, updated |
} else if let Some(float) = self | ||
.stacked | ||
.rev_iter() | ||
.find_map(|node| (*node).clone().node_into_float()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This clone can be avoided but it doesn't allocate so I don't think it makes much of a difference
Thanks! |
Right now if a workspace only contains a floating node, switching to that workspace will not change the currently focused window (without focus-follows-mouse doing its thing)