>
>
> As long as all are stable for the debounce time interval... I'm sure
> this approach is just fine for handling normal keypads. It certainly is
> efficient to have just one timer for N-switches. However, imagine you
> had one switch (or relay or whatever) that is constantly changing
> states. This unstable input prevents the debounce timer from ever
> terminating, which in turn means the other switches can not be read!


Sure, then you'd want to debounce that input separately.
My approach makes the assumption that all the switches in the group are
similar, and have similar response time needs.





> --
> Feel the power of the dark side!  Atmel AVR
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist