https://bugs.freedesktop.org/show_bug.cgi?id=99415
--- Comment #5 from Carlos Garnacho Parro <[email protected]> ---
FWIW, I think this is a worthwhile addition. I guess the event can be
reasonably sent on the same scroll sources that currently trigger the
0-movement events on scroll end.
And I do think too it's a good idea to split into a separate event type, it
will probably make sense to emit these events even if a 2fg operation on the
touchpad turns into a rotate/pinch gesture, and it seems more tractable to make
this a different event type than POINTER_AXIS.
Also +1 to making scroll start/end distinctive. On scroll end we do want to
keep the momentum, but on scroll start we do want to stop it. I guess both
cases might be put together as "apply the current velocity" trusting that it
will be 0 on scroll start, however this seems too high level knowledge, so IMO
would be great to have some kind of explicit hint from libinput.
--
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
