<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Double tap not always recognized" href="https://bugs.freedesktop.org/show_bug.cgi?id=90172#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Double tap not always recognized" href="https://bugs.freedesktop.org/show_bug.cgi?id=90172">bug 90172</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>Created <a href="attachment.cgi?id=115422" name="attach_115422" title="0001-touchpad-add-separate-shorter-timeout-for-doubletap.patch">attachment 115422</a> <a href="attachment.cgi?id=115422&action=edit" title="0001-touchpad-add-separate-shorter-timeout-for-doubletap.patch">[details]</a> <a href='page.cgi?id=splinter.html&bug=90172&attachment=115422'>[review]</a> 0001-touchpad-add-separate-shorter-timeout-for-doubletap.patch I don't think we can actually reduce the first tap timeout by much. If you hit a ~200ms delay on a "normal tap" (<a href="show_bug.cgi?id=90172#c9">comment #9</a>) then reducing it further risks missing it altogether. Note that we don't actually control the double click, we only convert tap to button clicks, everything else is handled in the client (GNOME has a doubleclick time setting). Here's a patch that reduces the second tap timeout, I think that's better to rely on. That should then also reduce the total time so we're more likely to be interpreted as a click in the default settings of the client.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>