GetKeyState() vs. GetAsyncKeyState() vs. getch()?

GetKeyState() and GetAsyncKeyState() are Windows specific APIs, while getch() works on other non-Windows-specific C compilers.

GetKeyState() gets the key status returned from the thread's message queue. The status does not reflect the interrupt-level state associated with the hardware.

GetAsyncKeyState() specifies whether the key was pressed since the last call to GetAsyncKeyState(), and whether the key is currently up or down. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState().

What I've seen in practice is that if you hold a key pressed and assign a behavior when the key is pressed, if you use GetKeyState(), the behavior will be called more times than if you'd have used GetAsyncKeyState().

In games, I prefer using GetAsyncKeyState().

(You can also check for more details on the MSDN blog).

Think what async means.

• GetAsyncKeyState() gets the key state asynchronously, i.e., without waiting for anything, i.e. NOW.

• GetKeyState() gets the key state synchronously, it is the key state of the key that you are about to read with getch(). It is queued in the keyboard buffer along with the keypresses themselves.

As an example, imagine the following has been typed, but hasn't yet been read:

• h
• i
• shift+1
• ctrl(held down)

GetAsyncKeyState() will return ctrl pressed

GetKeyState() will returnH presseduntil you callgetch()`

GetKeyState() will then return I pressed until you call getch()

GetKeyState() will then return shift pressed, 1 pressed until you call getch(), which will return ! (result from pressing shift+1)

GetKeyState() will then return ctrl pressed