??? 03/30/10 01:12 Read: times |
#174614 - Majority of implementations synchronizes with key down Responding to: ???'s previous message |
No, the billions of computers does not have keyboards that produce the main key event when the button is released.
They produce the key-down event directly after whatever debounce that is made. Besides the initial key-down event, you can then get (depending on type of key pressed) repeated key events while the key is pressed, with an initial delay and a repeat delay. And you get a key-up event when the button is released. But keypads where the action is performed on key release is very uncommon, and I would suspect that they are the result of not too skilled developers or not too clever product owners. In some games, actions are performed on the key-up, to let the user control how "hard" they do something by controlling how long they keep the button pressed. But that is a special case. For "normal" designs, key-up activation is a design fault. |
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 |