I'm trying to develop a screen locker for the Prizm (this time, I'll finish this project, I promise!). I have a few problems regarding the keyboard input.

The first is well known: the keyboard is too sensitive and key debouncing is needed. My difficulty is: I searched the forum and I could not find a definitive answer to key debouncing with non-blocking input (i.e. using GetKeyWait_OS). Can someone do the favor of explaining in a simple way, and preferably with code examples, how to do key debouncing?

The other question is related to the values GetKeyWait_OS returns.
I'm using the following to detect a pressed key on the keyboard:

Code:


If a key is pressed the function will return something other than zero, and kcol will contain the "column" of the key, and krow the "row". The 1 before &key is to block the Menu key from actually showing the menu (so the calculator is "locked").
What is the value of kcol and krow for the various keys of the keyboard? I know kcol 4 and krow 9 are the "coordinates" for the Menu key. But the "columns" and "rows" system doesn't look like it follows the order of the keys in the keyboard, or else I'm very dumb and not seeing it.

Anticipated regards

Here's a chunk of code I use:


Code:



These functions are used to check the current state of a key in the key array during the current loop runthrough, or check the value from the last loop. It supports the best way, multiple key detection, with all of this. Here's how it would be used in the game loop:


Code:


Pretty simple to work with, and pretty flexible. It's basically what I put together for Raptor since I needed multiple key detection and bullet-button debouncing, and it's very flexible and works very very well.

I don't understand what mean "key debouncing", but you can use this function to read keyboard (non-blocking)


Code:

Ashbad's code solved my problem. What I meant was that I did not want a key to be recognized as pressed twice (e.g. on two GetKey results) while it had never been released.

By other words: pressing and holding a key counts as a single press (at least for a certain amount of time), so that it doesn't repeat a certain keypress like crazy.