On Mon Sep 29 16:11:12 2025 +0000, Vibhav Pant wrote:
> changed this line in [version 2 of the diff](/wine/wine/-/merge_requests/9053/diffs?diff_id=212787&start_sha=fac7c50e9d0e02db41bbb4e9337bf9b109f041a1#4a7233637d8ed883514827839177fa1b3895ba87_338_343)
Thanks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9053#note_117049
On Mon Sep 29 16:11:11 2025 +0000, Vibhav Pant wrote:
> changed this line in [version 2 of the diff](/wine/wine/-/merge_requests/9053/diffs?diff_id=212787&start_sha=fac7c50e9d0e02db41bbb4e9337bf9b109f041a1#48b3cd062caffaafb4341438e88acfd833efc49c_800_787)
Sure, thanks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9053#note_117048
There exist clients that disable hardware cursors, and instead draw a
software cursor during their renderloop. Such clients incorrectly cause
winewayland to enable relative pointer motion because winewayland thinks
the cursor is not visible, when it is in fact visible and just drawn by
the client instead.
Enabling relative pointer motion breaks compositors that simulate
wl_pointer from tablet tool motion. sway is one such compositor that
supports sending wl_pointer events for clients that don't understand
tablet-v2.
Fix this by not discarding absolute motion events even in the case that
relative pointer motion is active. When relative pointer was
implemented, winewayland didn't support SetCursorPos and accepting
absolute motion events would break mouselook in 3D games. However, now
it does support SetCursorPos so there should be no harm in accepting
absolute motion events as well.
This allows tablet devices to work with winewayland running badly
behaved clients that do software rendering of cursors on compositors
that do simulate wl_pointer from tablet motion, despite winewayland not
supporting tablet-v2 yet.
Signed-off-by: Gopal Prasad <llyyr.public(a)gmail.com>
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/9068