<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - IBM Scrollpoint mouse: libinput mouse scrolling speed insanely fast" href="https://bugs.freedesktop.org/show_bug.cgi?id=106036#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - IBM Scrollpoint mouse: libinput mouse scrolling speed insanely fast" href="https://bugs.freedesktop.org/show_bug.cgi?id=106036">bug 106036</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>the direction locking is very mild, it's supposed to help with vertical scrolling to not introduce any undue horizontal movement. There's a built-in trigger that needs to be exceeded before we start sending events for the other direction. It's definitely not a hard lock - you can scroll in all directions at all times. But your output above shows that it's (probably) working, you don't get any horiz movement in the vertical scroll even though, most likely, you have the odd horizontal event in the output. > Probably I should add a > struct normalized_coords unaccel; > instead of abusing wheel_degrees which was already declared in > fallback_flush_wheels() for a final version of the changes? yeah, that sounds good. I'm always in favour of localised variables that make the code more obvious, the compiler optimises them away anyway.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>