Quote Originally Posted by Charles Linquis View Post
And most people don't realize it, but you can have an interrupt on *ANY* pin - sort of. ........
So THERE! mister_e and pxidr84!
Sure, I classify that as slow background process

amgen, you just need to read the switch all the time, keep a reading of the previous(s) and compare them. Depending of your timer rate, you may want to make sure it is hold down for X interrupt. set a flag to say a switch is ready, Once done, and the button being read, you wait Y interrupt before reading another and "publish" it.

Tons of way to do so. But for sure, you don't want any PAUSE in an ISR.