COMMON: Expand a bit the KeyState documentation

This follows a bug that was found in the Lure engine where keycode
was used in a place where it should have used ascii.
This commit is contained in:
Thierry Crozat 2012-07-01 01:03:49 +01:00
parent c19df60092
commit 50136f43c7

View File

@ -248,7 +248,10 @@ struct KeyState {
* ASCII-value of the pressed key (if any). * ASCII-value of the pressed key (if any).
* This depends on modifiers, i.e. pressing the 'A' key results in * This depends on modifiers, i.e. pressing the 'A' key results in
* different values here depending on the status of shift, alt and * different values here depending on the status of shift, alt and
* caps lock. * caps lock. This should be used rather than keycode for text input
* to avoid keyboard layout issues. For example you cannot assume that
* KEYCODE_0 without a modifier will be '0' (on AZERTY keyboards it is
* not).
*/ */
uint16 ascii; uint16 ascii;