Quote:
Originally Posted by meynaf
If this ends up being a bug that's not in your code (e.g. Windows bug), there is an easy way to make a workaround. Simply keep the previous status of every key you use. When you reveive a key down, mark the key as being down - and if it was already down before, ignore the event. When you receive a key up, mark the key as being up.
|
Done this, but it does mean I'm processing an extra 100 interrupts per second (25 key down events * 2 keys * 2 interrupts each).
I've also contacted the keyboard manufacturer (WASD Keyboards). While I think it's Microsoft's drivers at fault, they're the people who should know, or at least want to know.
16 November 2019, 18:04
Similar Threads
