Comment by [email protected]:
General Comment:
(Please excuse me if this isn't the place to enter into a discussion - I'm
new to this)
While I take the point about delaying the output, I think the change you're
suggesting isn't going to be robust in the presence of noise. I can see it
would work for a physical button, where as soon as you see a state change,
you know it's going to stabilise to that changed state. I don't think it
wouldn't work well for other situations. For example, one of my projects
involves an analogue signal which I threshold to get a digital output. The
analogue signal isn't really under my control and there is noise in the
data. If the debouncer changed state immediately rather than waiting until
the state is stable, it wouldn't be usable in this situation.
Maybe there's scope for adding a new function though, if the changes needed
aren't too intrusive. I'll have a think...
For more information:
http://code.google.com/p/jallib/source/detail?r=3106
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
