<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)" href="https://bugs.freedesktop.org/show_bug.cgi?id=98839#c88">Comment # 88</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)" href="https://bugs.freedesktop.org/show_bug.cgi?id=98839">bug 98839</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>(In reply to Daniel van Vugt from <a href="show_bug.cgi?id=98839#c87">comment #87</a>) > I am happy to wait and see how the patch in <a href="show_bug.cgi?id=98839#c77">comment #77</a> goes in the wild but > I'm slightly less optimistic about it only taking 80ms. Comment in the code: If the finger is down for 80ms without seeing motion events, the firmware filters and we don't need a software hysteresis The solution isn't perfect, but that's the best heuristic we have so far. And it beats having a config option through 3 layers of stack that users have to enable or disable manually. And then me having to handle bugs because of broken configuration files 3 years down the track.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>