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

Switch work space via mouse wheel scroll not working consistently (seems to have to do with fullscreen / maximize) #70

Open
UndeadDevel opened this issue May 6, 2023 · 7 comments

Comments

@UndeadDevel
Copy link

Occurs now on Fedora 38 with version 28 of CHC, but occurred previously on Fedora 36 as well.

I've set the mouse wheel to be used for switching WS while hovering over the top edge of the screen. Most of the time it works, but sometimes it does not and it's not clear what the problem is. The triggers are set to work when fullscreen is enabled. When the problem does show up, it's always when either there is a window in fullscreen on that WS or I've just maximized a window on that WS, but most of the time fullscreen or maximize works fine without triggering the problem...I've not noticed any particular factor that might be causing it; it just seems to randomly stop working sometimes.
It's also unlikely to be a mouse issue, as I've gotten a new mouse recently and the problem was there before and still occurs occasionally now.

"Unfullscreening" or "unmaximizing" fixes the issue, even if I immediately put the window back into fullscreen / maximize.

@UndeadDevel UndeadDevel changed the title Switch work space not working consistently (seems to have to do with fullscreen / maximize) Switch work space via mouse wheel scroll not working consistently (seems to have to do with fullscreen / maximize) May 6, 2023
@G-dH
Copy link
Owner

G-dH commented May 6, 2023

This behavior has been introduced in GS 40, it used to be reliable before. That's why I added the "Reset all triggers" item to the CHC-E's panel menu, but it doesn't always help. I'm not sure what exactly triggers this behavior in the fullscreen mode. GS 40+ cannot even open the overview when the display is in the fullscreen mode, I had to work around that.

@UndeadDevel
Copy link
Author

Ah, I've been wondering why the panel menu was added...unfortunately, when the issue occurs while using the "fullscreen on empty WS" function, resetting doesn't fix it, at least in my attempts so far.
I'll report back if I find out how to reliably trigger the bug.

@UndeadDevel
Copy link
Author

Okay, so I've switched to wayland now from x11 and the issue seems to be gone...feel free to close; I'll report back if it returns but so far it seems it might've been xorg-related.

@UndeadDevel
Copy link
Author

Another interesting anecdote: mouse scroll reliably doesn't work to switch WS if there is a file transfer ongoing and I have clicked the status button in Nautilus to see how much time remains for the transfer, or making Nautilus open any other "info window", such as when clicking on the preferences button, even without an ongoing file transfer. When clicking somewhere else such that this "info window" disappears, it works again.
Not a big deal though.

@G-dH
Copy link
Owner

G-dH commented Dec 15, 2023

Any menu or context popup grabs all mouse events from the entire screen, so the CHC-E cannot get them.

@UndeadDevel
Copy link
Author

Any menu or context popup grabs all mouse events from the entire screen, so the CHC-E cannot get them.

Ah, good to know...I can't verify whether this issue is still a problem btw., so feel free to close. Reading my previous comments it seems like it was X11-specific, so if someone uses X11 and sees this issue, please comment to track it.

@G-dH
Copy link
Owner

G-dH commented Mar 7, 2024

The initial issue can likely be resolved by the Disable unredirect fullscreen windows extension. In the default configuration, the GNOME compositor manages regular windows, while in the case of fullscreen windows, the compositor is bypassed, allowing direct handling by the graphics card and resulting in improved performance.

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