| ??? 03/29/10 19:26 Modified: 03/29/10 19:30 Read: times |
#174604 - which is a $#@!! disaster Responding to: ???'s previous message |
It's worth noting that many keyboard scanners don't encode the keypress until it goes away
which is a $#@!! disaster. Just about the least user friendly 'feature' you can come up with. I have seen people press keys with all their might and strength to make whatever the key is supposed to do happen not being aware of the required release. DO NOT DO SO it was pretty important to have switches with very similar characteristics naah, you just debounce for worst case. E.g. with a 10 ms debounce it does not matter if a key in the rig debounces in 1ms or less Erik |
| Topic | Author | Date |
| switch input > interrupt (debouncing) | 01/01/70 00:00 | |
| double post | 01/01/70 00:00 | |
| Why the extra hardware? | 01/01/70 00:00 | |
| wow | 01/01/70 00:00 | |
| other ISR recommendation | 01/01/70 00:00 | |
| or the other solution (my favorite) | 01/01/70 00:00 | |
| using timer | 01/01/70 00:00 | |
| Some switches have very long bounce time | 01/01/70 00:00 | |
| a lot depends on the switches themselves | 01/01/70 00:00 | |
| which is a $#@!! disaster | 01/01/70 00:00 | |
| Remember that there is more than push buttons out there | 01/01/70 00:00 | |
| What about the others? | 01/01/70 00:00 | |
| Majority of implementations synchronizes with key down | 01/01/70 00:00 | |
| Now I'm confused ... | 01/01/70 00:00 | |
| Not Sure About The Code | 01/01/70 00:00 | |
More info on PC keyboard | 01/01/70 00:00 | |
| Short spikes | 01/01/70 00:00 | |
| The real problem with debouncing | 01/01/70 00:00 |