<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c20">Comment # 20</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 <span class="vcard"><a class="email" href="mailto:freedesktop@tlvince.com" title="Tom Vincent <freedesktop@tlvince.com>"> <span class="fn">Tom Vincent</span></a>
</span></b>
<pre>I'm experiencing the same issue as described here with hysteresis. In the long
term, a knob per <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Hard to position a cursor on Thinkad X1 Carbon 3rd gen after f6c2d4b8b5e1968411568d81b47488a655ba47a1."
href="show_bug.cgi?id=94379#c29">bug 94379, comment 29</a> is needed. In the meantime, I've been
having a look at restoring the "PRECISE_TOUCHPAD" flag to disable hysteresis.
(In reply to Peter from <a href="show_bug.cgi?id=98839#c12">comment #12</a>)
<span class="quote">> Have a look at commit afdcaf50157c0a76389740885bed3719b758dc37, that provides > a blueprint for the patch required to mark your touchpad as one that doesn't > require hysteresis. I'm willing to give in here to see whether we'll see any > pushback (see 27078b2). Happy to review and merge a patch for this.</span >
I'd be interested to hear your thoughts on:
<a href="https://github.com/tlvince/libinput/compare/tlvince:7272696...tlvince:9259143">https://github.com/tlvince/libinput/compare/tlvince:7272696...tlvince:9259143</a>
Note, this doesn't restore the tag on Apple and Lenovo *40 devices. I'm aware
hysteresis has been enabled/reverted a few times (e.g.
48473994c8e60189356feae7b7eae25288e5ac28) and I agree maintaining a list of
device-specific flags is unscalable, but this is a real issue[1] for some users
and this seems the easiest way to do it _right now_ (it could be again removed
once suitable user-facing configuration is in place).
[1]:
<a href="https://www.reddit.com/r/archlinux/comments/52makr/fyi_libinput_works_much_better_than_synaptics_on/dadogfd/?st=j12aqwqi&sh=ec733a11">https://www.reddit.com/r/archlinux/comments/52makr/fyi_libinput_works_much_better_than_synaptics_on/dadogfd/?st=j12aqwqi&sh=ec733a11</a>
<a href="https://bbs.archlinux.org/viewtopic.php?id=224643">https://bbs.archlinux.org/viewtopic.php?id=224643</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>