<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Change scroll thresholds to work as motion/time" href="https://bugs.freedesktop.org/show_bug.cgi?id=85991#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Change scroll thresholds to work as motion/time" href="https://bugs.freedesktop.org/show_bug.cgi?id=85991">bug 85991</a> from <a class="email" href="mailto:jwrdegoede@fedoraproject.org" title="Hans de Goede <jwrdegoede@fedoraproject.org>"> Hans de Goede</a> <pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=85991#c0">comment #0</a>) > The scroll threshold is triggered by a single event exceeding the built-in > threshold. This means it relies on the sampling rate of the device, devices > with lower sampling rate are more likely to have high-enough deltas. Ack to changing the threshold to a speed threshold, rather then a move length threshold. > Likewise, continuous motion just below the threshold never triggers > scrolling. Right, this is intentional, because if you want to say scroll only vertical and do a large vertical sweep, the motion will never be exactly 90 degrees to the bottom edge, iow it will always have some x component in there, and a little x component for each event since the movement is at say 88 degrees from the horizontal, we do NOT want to accumulate those x deltas as otherwise any attempt to purely scroll vertical will sooner or later cross the threshold and we will also start sending out horizontal scroll events.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>