| 4 | | Although the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the preemptive multitasking nature of Windows, another application can call GetAsyncKeyState and receive the "recently pressed" bit instead of your application. The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon. |
| | 4 | Although the least significant bit of the return value indicates whether the key has been |
| | 5 | pressed since the last query, due to the preemptive multitasking nature of Windows, another |
| | 6 | application can call GetAsyncKeyState and receive the "recently pressed" bit instead of your |
| | 7 | application. The behavior of the least significant bit of the return value is retained |
| | 8 | strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and |
| | 9 | should not be relied upon. |
