-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
compositor: Configurable behavior when window to be focused conflicts with fullscreen #12033
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
Conversation
2db1f1f to
7fa6e12
Compare
cc0add1 to
2eeb053
Compare
6e75eb1 to
610c6c4
Compare
610c6c4 to
6979088
Compare
c2663bd to
b8812bc
Compare
|
I pushed a sizeable refactor to clean up the code in general. LMK if everything still works fine. |
|
should be good now |
|
did I accidentally nuke your fix? Sorry if that happened but yeah tests fail on kitty_activating again xD |
|
It appears that the execution continues after Is it a bug? |
|
No, we need to waitUntilWindowsN Forcekill sends SIGKILL, but it can take a few frames before the window disappears. |
3a8ff55 to
8baea79
Compare
… with fullscreen Renames `misc:new_window_takes_over_fullscreen` into `misc:on_focus_under_fullscreen` and implements the following behavior: - By default, when a tiling window is being focused on a workspace where a fullscreen/maximized window exists, respect the `misc:on_focus_under_fullscreen` config variable.
|
Okay, fixed the test. Would you accept a PR renaming the kill* and forcekill* dispatchers to something that describes their functionality more accurately? |
|
probably not? They do what they say... |
|
thanks :) |
|
(quotes from the wiki)
|
|
the first one is just a relic and we didnt want to change it to avoid silent config breaks |
|
This broke hy3: |
|
great. It needs to be updated. |
|
This broke |
|
As this is 1 single commit with multiple and huge changes, it is difficult for me to see where the regression was introduced. Could you send your original patch without vaxry's changes to check it please? |
|
Yeah, I agree, huge single-commit changes make it much harder to trace things back. I wish we made commits more granular. Unfortunately, the initial refactoring by vaxry was also pushed as a single commit. Here it is: 16a5f7b (some fixes were applied later) |
|
I am trying to see your original changes without hyprfucker's huge changes. Are they lost? |
|
You can use the commit that I shared and take a look at its parent commits. The ones authored by me contain the original changes. But they are probably irrelevant anyway, since the refactoring has rewritten the parts that I was working on (most of them, at least). Also, why would you use this rude kind of language? I don't think it's appropriate |
|
I need to joke to not lose my mental sanity, sorry, not trying to be rude though, just for fun. |
hey go fuck yourself |
Describe your PR, what does it fix/add?
Implements the following behavior:
By default, when a tiling window is being focused on a workspace where
a fullscreen/maximized window exists, respect
the
misc:new_window_takes_over_fsconfig variable.When a tiling window is focused with the
focuswindowdispatcher,respect the same config variable, unless it is set to 0 (ignore).
In that case, the window to be focused takes over fullscreen.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Please, see my review comments on GitHub.
Is it ready for merging, or does it need work?
Did not implement tests yetShould be merged together with hyprwm/hyprland-wiki#1267