Mouse clicks not properly delivered when in Global workspace mode #161
Assignees
Comments
|
Oh fun, I wonder what broke this, as this definitely used to work... This function should translate from global coordinates to workspace-relative coordinates. Which should be the same coordinate space, in global-workspace-mode, which makes the issue more perplexing. For output-local-workspaces the translating basically remaps the event to be relative to the output. I guess somewhere we are missing this translation call.. |
ids1024
added a commit
that referenced
this issue
Sep 13, 2023
I didn't see any issue with how mouse events were handled, but a bisect showed b818a68 caused the issue. Reverting the definition of `element_under` to the version before that change Comparing what both versions return, the right element is returned, but the location returned is wrong. This makes the return value match the position that was returned by the previous implementation. It seems to be working correctly now. Fixes #161.
ids1024
added a commit
that referenced
this issue
Sep 13, 2023
I didn't see any issue with how mouse events were handled, but a bisect showed b818a68 caused the issue. Reverting the definition of `element_under` to the version before that change fixed the behavior. Comparing what both versions return, the right element is returned, but the location returned is wrong. This makes the return value match the position that was returned by the previous implementation. It seems to be working correctly now. Fixes #161.
ids1024
added a commit
that referenced
this issue
Sep 13, 2023
I didn't see any issue with how mouse events were handled, but a bisect showed b818a68 caused the issue. Reverting the definition of `element_under` to the version before that change fixed the behavior. Comparing what both versions return, the right element is returned, but the location returned is wrong. This makes the return value match the position that was returned by the previous implementation. It seems to be working correctly now. Fixes #161.
|
Took a while to track it down, but #172 seems to fix this. |
|
This is still an issue for the cosmic panel, if it is running on the middle display in a three display setup. |
|
Re-opening, since the cosmic panel is not receiving mouse clicks when on the middle display in a three display setup, while using Global worskpace mode. |
18 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Global workspaces mode, with three monitors arranged horizontally, I often cannot click on controls on windows that are on the second and third monitor.
The text was updated successfully, but these errors were encountered: