xserver/hw
Vlad Zahorodnii 60f0bfe852 xwayland: Dispatch tablet tool tip events after frame events
Xwayland dispatches tablet tool tip events immediately when they arrive.

With compositors such as mutter and sway, it is not an issue because
their libinput backends synthetize axis events before tip events. In
other words, axis data and the tip status belong to different frames.

On the other hand, kwin sends axis and tip events in a single frame
(its libinput backend generates a single tip event with axis data
attached to it). Since the tip events are dispatched immediately,
they can have wrong information associated with them, for example tool
position or pressure. It results in undesired "streaks" when the user
presses the tablet tool against the tablet.

See also https://bugs.kde.org/show_bug.cgi?id=479856.

Signed-off-by: Vlad Zahorodnii <vlad.zahorodnii@kde.org>
Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/2032>
2025-06-25 11:44:07 +00:00
..
kdrive Revert "kdrive: use dixDestroyPixmap() instead of direct driver call" 2025-06-17 20:02:16 +00:00
vfb Revert "vfb: use dixDestroyPixmap() instead of direct driver call" 2025-06-17 20:02:16 +00:00
xfree86 Revert "os: log: replace LogMessageVerbSigSafe() by LogMessageVerb()" 2025-06-24 23:40:51 +00:00
xnest Revert "mi: unexport miWindowExposures()" 2025-06-24 10:52:53 -07:00
xquartz man pages: remove extraneous PP macros 2025-05-31 15:01:49 -07:00
xwayland xwayland: Dispatch tablet tool tip events after frame events 2025-06-25 11:44:07 +00:00
xwin Revert "xwin: drop duplicate OsVendorVErrorF()" 2025-06-24 23:40:49 +00:00
meson.build meson.build: print a summary of the DDX to build 2025-03-24 03:05:35 +00:00