Differences between version 2 and previous revision of SDL_keysym(3).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Monday, June 3, 2002 6:53:50 pm | by perry | Revert |
| Older page: | version 1 | Last edited on Monday, June 3, 2002 6:53:50 pm | by perry | Revert |
@@ -36,9 +36,9 @@
The __SDL_keysym__ structure is used by reporting key
presses and releases since it is a part of the
-__SDL_KeyboardEvent__.
+__SDL_!
KeyboardEvent__.
The __scancode__ field should generally be left alone, it
is the hardware dependent scancode returned by the keyboard.
@@ -49,10 +49,10 @@
.
.
-while(SDL_PollEvent(
-__mod__ stores the current state of the keyboard modifiers as explained in __SDL_GetModState__. The __unicode__ is only used when UNICODE translation is enabled with __SDL_EnableUNICODE__. If __unicode__ is non-zero then this a the UNICODE character corresponding to the keypress. If the high 9 bits of the character are , then this maps to the equivalent ASCII character:
+while(SDL_!
PollEvent(
+__mod__ stores the current state of the keyboard modifiers as explained in __SDL_!
GetModState__. The __unicode__ is only used when UNICODE translation is enabled with __SDL_EnableUNICODE__. If __unicode__ is non-zero then this a the UNICODE character corresponding to the keypress. If the high 9 bits of the character are , then this maps to the equivalent ASCII character:
char ch;
if ( (keysym.unicode
