Thread (7 messages) 7 messages, 4 authors, 2018-12-18

Re: [rfd] saving old mice -- button glitching/debouncing

From: Pavel Machek <hidden>
Date: 2018-12-15 10:29:08
Also in: lkml

On Sat 2018-12-15 11:12:21, Vojtech Pavlik wrote:
On Sat, Dec 15, 2018 at 10:47:22AM +0100, Pavel Machek wrote:
quoted
quoted
quoted
b) would it be acceptable if done properly? (cmd line option to
enable, avoiding duplicate/wrong events?)
Well, for one, you shouldn't be using a timer, all the debouncing can be
done by math on the event timestamps.
Not... really, right? You need to send an release some time after
button indicates release if bounce did not happen. It is similar to
autorepeat needing a timer.
You can send the first release and ignore all presses and releases in a
time window after that.
I could, and it would work for glitches on release, but that would do
very bad things if switch glitched on press, right?

"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XX           " ->
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX              " ... ok

"XX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX..." ->
"XX                                  ..." ... bad idea. [Maybe could be
detected with "XX " being unusually short?]

But I believe I see 

"XXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXX" on X220 device, too.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help