https://bugs.freedesktop.org/show_bug.cgi?id=106113
--- Comment #6 from Peter Hutterer <[email protected]> ---
> when it's more obviously wrong (user is trying to scroll)
pinch in libinput is pinch-and-rotate and thus includes the moving component
with it. So it's really hard to figure out what the user intended based on the
data we get from the touchpad because a pinch+move gives us the same data as a
pinch+scroll. There likely are options to improve on this but so far no-one's
found the time for it.
> 2. Comment 3 triggers this bug too
It does. In the output there we have:
> event16 - touch-size: end touch
So this indicates a touch threshold issue. Having said that, immediately after
there's
> event16 - button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP
> to BUTTON_STATE_NONE
which would indicate a released physical button. At that point it gets hard to
guess what really happened.
Note that I can only go on the data that the recording provides, I can't guess
what you've been doing on the touchpad. So please keep any recordings/logs as
simple and self-contained as possible.
--
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
