https://bugs.freedesktop.org/show_bug.cgi?id=105043
Peter Hutterer <peter.hutte...@who-t.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #23 from Peter Hutterer <peter.hutte...@who-t.net> ---
> event10 - tap: touch 0 state TAP_STATE_TOUCH_2 → TAP_EVENT_MOTION →
> TAP_STATE_TOUCH_2_HOLD
That's still the problem here, a motion event after the second finger down
causes it to not detect the tap. I think this may be related to how we handle
semi-mt touchpads too, because we treat them effectively as single-finger
touchpads. In the 20.550366 event you get a large finger movement as slot 1
ends but because we process slots in order, I wonder if that triggers a bug
where we think there's movement before we realise it's part of the finger up.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
