-
Notifications
You must be signed in to change notification settings - Fork 135
Cannot perform touch events on non-focused monitor #655
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
Comments
This might also occur with a single touch monitor and a non-touch monitor, if the mouse is in the non-touch monitor. |
This is likely because of the StackOverlay actor that gets enabled on monitors where the mouse isn't. See this thread where I talk a bit about this peterfajdiga/karousel#3 It's basically how we do a "per monitor workspace". |
Uncomment these lines to see the overlay (that's most likely blocking your touch events): https://github.com/paperwm/PaperWM/blob/release/stackoverlay.js#L282-L283 |
So basically, hooking This would also mean, check that if the mouse starts moving again on a monitor that was defocused by a touch event, the switch triggers again properly |
In principle yes - making stackoverlay reactive to touch should cause that monitor space to Also, yes, the mouse movement should trigger the mouse-monitor to become active. |
hm, regression seems to have happened at some point during #751 merge, or I did not test focus behavior properly. |
Closed (again, hopefully for good 😅) by #759 |
Describe the bug
GNOME is capable of handling multiple monitors, each with their own touch surface. When PaperWM is active, touch screen events are discarded for all apps on displays other than the currently focused one, and I need to move the mouse to the other display to use the touch screen on it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The other window reacts properly to touch events
System information:
Additional context
Native GNOME without PaperWM lets touch events through to unfocused monitors.
The text was updated successfully, but these errors were encountered: