<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Two-finger scrolling jumpy with Synaptics touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=91135#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Two-finger scrolling jumpy with Synaptics touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=91135">bug 91135</a> from <a class="email" href="mailto:benjamin.tissoires@gmail.com" title="Benjamin Tissoires <benjamin.tissoires@gmail.com>"> Benjamin Tissoires</a> <pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=91135#c14">comment #14</a>) > before this, slot 0 is on 3481/2721, slot 1 is on 4224/1777. In the event > where the slot 1 ends slot 0 jumps to slot 1 positions *for a single event*. > In the next event it is back to 3478/2702, i.e. the previous slot 0 position. > > Benjamin, is this something we can detect in the kernel or do I need to work > around it? This is a semi-mt buttonpad. I can't figure out which code path we manage to trigger here. But it's unlikely the kernel will be able to fix those jumps. I think the best course of action is to ignore/reset the coordinates when the contact count changes. SEMI_MT are such a pain :(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>