https://bugs.freedesktop.org/show_bug.cgi?id=91135
Peter Hutterer <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
| |m
--- Comment #14 from Peter Hutterer <[email protected]> ---
This event here is the problem:
E: 1.469012 0003 0035 4220 # EV_ABS / ABS_MT_POSITION_X 4220
E: 1.469012 0003 0036 1777 # EV_ABS / ABS_MT_POSITION_Y 1777
E: 1.469012 0003 002f 0001 # EV_ABS / ABS_MT_SLOT 1
E: 1.469012 0003 0039 -001 # EV_ABS / ABS_MT_TRACKING_ID -1
E: 1.469012 0003 0000 4220 # EV_ABS / ABS_X 4220
E: 1.469012 0003 0001 1777 # EV_ABS / ABS_Y 1777
E: 1.469012 0003 001c 0004 # EV_ABS / ABS_TOOL_WIDTH 4
E: 1.469012 0001 0145 0001 # EV_KEY / BTN_TOOL_FINGER 1
E: 1.469012 0001 014d 0000 # EV_KEY / BTN_TOOL_DOUBLETAP 0
E: 1.469012 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +25ms
before this, slot 0 is on 3481/2721, slot 1 is on 4224/1777. In the event where
the slot 1 ends slot 0 jumps to slot 1 positions *for a single event*. In the
next event it is back to 3478/2702, i.e. the previous slot 0 position.
Benjamin, is this something we can detect in the kernel or do I need to work
around it? This is a semi-mt buttonpad.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
