[Wayland-bugs] [Bug 85991] Change scroll thresholds to work as motion/time

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=85991

--- Comment #2 from Peter Hutterer <peter.hutterer at who-t.net> ---
I think there are two stages: triggering the initial scroll which can be
distance-based so that a tentative movement can still trigger scrolling (e.g.
if the user wants to scroll by a few pixels only they can't move too fast).

Then there's the scroll direction lock, once vscroll starts there should be a
slight bias against hscroll to start and that's where speed is better than
distance.

In the long run though we shouldn't be too worried about getting scroll locking
to work perfectly in libinput. I think this is something where we aid a bit but
the exact behaviour is up to the toolkit to handle when a scroll direction
should be locked or not. It is something that may be different for each widget.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20141110/5636a61b/attachment.html>