Timeline for What design patterns can I use to handle user input and display updating?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2014 at 9:48 | history | edited | Krista K | CC BY-SA 3.0 |
fixed spelling error and added credit for the menu structure source
|
| Mar 6, 2014 at 9:27 | comment | added | Krista K | @Cybergibbons ah, didn't see any mention of a display. The one I like is a ready made shield, cheap enough, and you can do things with colors. Here's a build report of my most recent project: forums.adafruit.com/… | |
| Mar 6, 2014 at 7:37 | comment | added | Cybergibbons | Sorry for all the questions - why a TFT? I'm currently working with a 128x64 LCD which has a lot of benefits (mainly being physically large). Also cheap. | |
| Mar 6, 2014 at 7:30 | comment | added | Cybergibbons | I find debounce often isn't required, but some switches seem to be much noisier than others. The upright, edge mounted PCB tactile switches seem the worst by far, maybe because instead of pressing, users often lever these forwards. Debouncing is so easy that I nearly always do it now. | |
| Mar 6, 2014 at 7:27 | comment | added | Cybergibbons | I like the way you've done that - it's understandable, clean, and very small in size. I had been looking at using a library (MenuBackend) but it is hard to understand for new programmers (using callbacks) and can't sit in PROGMEM. | |
| Mar 6, 2014 at 1:17 | history | answered | Krista K | CC BY-SA 3.0 |