Timeline for Debouncing buttons
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2010 at 18:59 | comment | added | Kortuk | You need to make sure to debounce any signal that could damage your controller in software. Then you strike a balance between processor time and hardware cost. | |
| Nov 18, 2010 at 8:10 | comment | added | Vincent Van Den Berghe | If that is the consensus/general rule then indeed, there is no need for more examples. | |
| Nov 17, 2010 at 23:17 | comment | added | Kortuk | @Vincent, Kellenjb summed it up on his answer how to decide. I did not click your link because it had a funny name, now that I clicked it I see ganssle! | |
| Nov 17, 2010 at 22:41 | comment | added | Vincent Van Den Berghe | Would you mind summing up a few use cases to illustrate when to use soft/hardware? (this is probably subjective, but I'd like some examples anyway) | |
| Nov 17, 2010 at 22:34 | comment | added | Vincent Van Den Berghe | The ganssle article was the reason I asked this question, it's linked in my question :) Thanks for the link to the debounce code snippets. | |
| Nov 17, 2010 at 15:50 | comment | added | Kortuk | I was going to go get a link to ganssle when I saw the question. | |
| Nov 17, 2010 at 14:38 | history | answered | Toby Jaffey | CC BY-SA 2.5 |