osc.lua: fix element touch handling #16468
Conversation
|
Do you think this shouldn't be fixed in input.c for consistent mouse up behavior for all scripts, not only in osc.lua? |
This would require that mouse movements being ignored during the timeout period after all touch points are removed, and clients cannot get any updates to the In other words, because information loss in the process, clients are not able to handle this properly, unlike the current approach using up to date mouse + touch position data. |
|
could you fix typo in commit title? |
On some compositors, when all touch points disappear the compositors reset the mouse position, which moves the mouse out of the osc element trigger area so mouse up events do not happen. Fix this by tracking the last touch position and use that as the virt mouse position if the screen is recently touched.
na-na-hi
changed the title
|
Download the artifacts for this pull request: Windows |
On some compositors, when all touch points disappear the compositors reset the mouse position, which moves the mouse out of the osc element trigger area so mouse up events do not happen.
Fix this by tracking the last touch position and use that as the virt mouse position if the screen is recently touched.