<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Touchpad does not feel "right", acceleration issue" href="https://bugs.freedesktop.org/show_bug.cgi?id=90735#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Touchpad does not feel "right", acceleration issue" href="https://bugs.freedesktop.org/show_bug.cgi?id=90735">bug 90735</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>evemu is simply sudo evemu-record /dev/input/eventX, with your device. Starting it without arguments will produce a list of devices. (In reply to Britt Yazel from <a href="show_bug.cgi?id=90735#c4">comment #4</a>) > I have a synaptics touchpad. The one in the Dell XPS 13 9333. right, that's one with resolution. good enough then. fwiw, some touchpads provide physical resolutions, others don't. we're generally better on the ones that do because we can deal with physical movements over guesstimates based on device units. > I am testing the libinput 0.17 with the low velocity patch, and I think it > is an improvement. That being said, it still feels a bit off. If I get the > acceleration right for medium speed cursor movements, a quick movement sends > me flying over my target. And if I set it right for quick movements, medium > speed movements cause me to undershoot. Slow cursor speeds seem to be ok now > though. right, I agree on the quick movement being off, especially on touchpads. looking into this already, but don't have anything to show yet. we currently use the same pointer acceleration function for touchpads and mice, but I think the profile of the functions needs to be different. > Lastly, what is the rationale against having separate settings for both > acceleration and velocity, and rather this dynamically changing acceleration? reluctance to expose too many knobs for user configuration. Every knob added multiplies the testing and maintenance effort. also, anything that's user-configurable will be (mis)used, potentially preventing improvements down the road. So the knobs that we do expose should be there for a reason and not just short-term fixes because something isn't working as expected right now.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>