<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - RFE: keyboard debouncing" href="https://bugs.freedesktop.org/show_bug.cgi?id=105222#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - 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>Created <a href="attachment.cgi?id=137713" name="attach_137713" title="keyboard state redux">attachment 137713</a> <a href="attachment.cgi?id=137713&action=edit" title="keyboard state redux">[details]</a> keyboard state redux Peter, thanks for the quick response and the in-depth analysis. Your keyboard-state.py is a useful tool and I hope it will live on. You are looking for bounces by looking for any two consecutive events that are closely separated. I believe that approach will not work. Instead, we need to look for two successive key down events from the *same key* that occur too closely together. I've modified keyboard-state.py to do exactly this, using a bounce threshold of 70 ms. I ran it on my event recording and have attached the output. It detects exactly the bounces that occurred as I was typing, including one that I didn't mention previously (a bounced "n") since I backspaced over it immediately after it occurred. Here they are: 10.773511 - after "even" 11.235823 - after "with" 15.791665 - after "I'm" 16.211357 - after "still" 66.204838 - 'n' in "key repeating" 72.104026 - before "double" 86.092569 - before "The delay" I believe this shows that bounce detection is viable, at least for my keyboard. I'll make a pull request at your github site with my changes to keyboard-state.py, in case you want them. You've said that you are reluctant to fix this in libinput. I guess the question then comes down to this: would you accept a patch to add keyboard debouncing along these lines?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>