type=SDL_KEYDOWN or key_state=SDL_
then an SDL_RELEASED when released and pressed again. For these keys KEYUP and KEYDOWN events are therefore
analogous to the state of the caps lock and num lock LEDs rather than the keys themselves.
These special cases are required for compatibility with Sun workstations.
-Note: Repeating SDL_KEYDOWN events will occur if key repeat is enabled (see enable_key_repeat (enable_key_repeat in SDL::EVENTS)).
+Note: Repeating SDL_KEYDOWN events will occur if key repeat is enabled (see enable_key_repeat ("enable_key_repeat" in SDL::EVENTS)).
key_state
@@ -303,7 +303,7 @@ This field is very useful when you are checking for certain key presses, like so
key_unicode
-The unicode field is only used when UNICODE translation is enabled with enable_unicode (enable_unicode in SDL::EVENTS).
+
The unicode field is only used when UNICODE translation is enabled with enable_unicode ("enable_unicode" in SDL::EVENTS).
If unicode is non-zero then this is the UNICODE character corresponding to the keypress.
If the high 9 bits of the character are 0, then this maps to the equivalent ASCII character:
my $char;
@@ -332,7 +332,7 @@ button states (motion_state).
motion_state
-The button state can be interpreted using the SDL_BUTTON macro (see get_mouse_state (get_mouse_state in SDL::EVENTS)).
+The button state can be interpreted using the SDL_BUTTON macro (see get_mouse_state ("get_mouse_state" in SDL::EVENTS)).
motion_x, motion_y