<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#c7">Comment # 7</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>oki, that diff looks good. but after digging around a bit more I think we need a few extra bits here. Luckily they're already in place. Basically, we want evdev_post_scroll() to handle the scroll events because it handles things like direction locking. Much more convenient and you don't get stray horizontal scrolls. That function takes unaccelerated coordinates (normalized), see fallback_flush_relative_motion() for how to get them. Basically call normalize_delta() on them and done. The overall goal is that you don't need the CLICK_ANGLE properties because they don't make sense on this device, you don't have a click angle because you don't have a wheel that clicks. If you need those it indicates that your EVDEV_MODEL_SCROLLPOINT flag isn't taking and you're still falling back to the old click method. A few printfs should verify that. But as long as the click angle properties affect your device it means there's a bug in the new code because it should be completely separate :) 70-mouse.hwdb is part of systemd btw but again, we don't need that change.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>