<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - RFE: keyboard debouncing" href="https://bugs.freedesktop.org/show_bug.cgi?id=105222#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - RFE: keyboard debouncing" href="https://bugs.freedesktop.org/show_bug.cgi?id=105222">bug 105222</a> from <a class="email" href="mailto:adam@medovina.org" title="Adam Dingle <adam@medovina.org>"> Adam Dingle</a> <pre>Thanks for reopening this feature request and being willing to consider this at least. Actually in the version of the script I gave you the threshold is 70 ms, not 30 ms. Some of the bounces I observed took nearly 70 ms, so a lower threshold would not detect them all. I was typing fairly quickly when I made the key recording that I attached earlier and the script doesn't find any false positives there, so I think a threshold around 70 ms may be reasonable. Still, if we do add a keyboard bouncing feature to libinput I think it should be off by default (or perhaps enabled with a very low threshold, which is basically equivalent). A user who has a bouncy keyboard should be able to turn it on and set the threshold, either via a configuration setting or (maybe at some point) through a GUI panel in the system keyboard settings. I think it may be hard to find a single threshold value that works perfectly for everyone, hence the need to let users set it. Anyway, you said there is some chance you would accept a patch like this if it is not too complex, though you are not enthusiastic. I have a strong personal need for this feature so I may look into this, unless I buy a new laptop first, which is another way to fix the problem. :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>