<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)" href="https://bugs.freedesktop.org/show_bug.cgi?id=98839#c57">Comment # 57</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 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>doh, I thought I had pushed the !enabled fixed, done now and force-pushed so the branch is up-to-date and ready for testing. Thanks for spotting that. Commit is currently 1b251c2676130 but I may need to push more later. The current event count of 5 means holding the finger stationary for ~60ms on most touchpads. That's short enough that I can trigger it here even when trying not to, usually it triggers before I even start moving the fingers, right after I place it on the touchpad for the first time. That's on a T440 which is equivalent to the X1 3rd iirc, so an older touchpad. I recommend testing with sudo ./build/libinput-debug-events --verbose, that prints a message when the hysteresis is disabled. If the message appears, then hysteresis is ignored. Nate: <a href="attachment.cgi?id=135028" name="attach_135028" title="Nate Graham - single finger held still for 10s">attachment 135028</a> <a href="attachment.cgi?id=135028&action=edit" title="Nate Graham - single finger held still for 10s">[details]</a> has several non-moving event streams that last a second or even longer. So it should definitely activate on your touchpad. I tested all the attachments above (still and moving) and they all disable the hysteresis within the first fraction of a second, before the first events come out of the device. The only case where the period may be significantly longer than 60ms would be if the touchpad firmware filters pressure and you don't get *any* events before the next motion event some time later. That can happen, see E 1.557756 in Nate's <a href="attachment.cgi?id=135029" name="attach_135029" title="Nate Graham - slow movements left then up">attachment 135029</a> <a href="attachment.cgi?id=135029&action=edit" title="Nate Graham - slow movements left then up">[details]</a> which is 119ms after the previous one. But that is the exception. Needs fixing, sure, but a very niche issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>