|
Size: 3916
Comment: Updated.
|
Size: 4135
Comment: Updated notes on SDL_QUIT
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 72: | Line 72: |
| An SDL_QUIT event is generated when the user tries to close the application window. If it is ignored or filtered out, the window will remain open. If it is not ignored or filtered, it is queued normally and the window is allowed to close. When the window is closed, screen updates will complete, but have no effect. | An SDL_QUIT event is generated when the user tries to close the last remaining SDL_Window. If it is ignored or filtered out, the window will remain open. If it is not ignored or filtered, it is queued normally and the window is allowed to close. When the window is closed, screen updates will complete, but have no effect. On Mac OS X, pressing Command-Q (the standard keyboard shortcut for "Quit this application") will cause SDL to generate an SDL_QUIT event. The application is still responsible for terminating itself, however. |
DRAFT |
SDL_EventType
An enumeration of the types of events that can be delivered.
Contents
Values
SDL_FIRSTEVENT |
do not remove (unused) |
Application events |
|
SDL_QUIT |
user-requested quit; see Remarks for details |
Android and iOS events |
|
SDL_APP_TERMINATING |
|
SDL_APP_LOWMEMORY |
|
SDL_APP_WILLENTERBACKGROUND |
|
SDL_APP_DIDENTERBACKGROUND |
|
SDL_APP_WILLENTERFOREGROUND |
|
SDL_APP_DIDENTERFOREGROUND |
|
Window events |
|
SDL_WINDOWEVENT |
window state change |
SDL_SYSWMEVENT |
system specific event |
Keyboard events |
|
SDL_KEYDOWN |
key pressed |
SDL_KEYUP |
key released |
SDL_TEXTEDITING |
keyboard text editing (composition) |
SDL_TEXTINPUT |
keyboard text input |
Mouse events |
|
SDL_MOUSEMOTION |
mouse moved |
SDL_MOUSEBUTTONDOWN |
mouse button pressed |
SDL_MOUSEBUTTONUP |
mouse button released |
SDL_MOUSEWHEEL |
mouse wheel motion |
Joystick events |
|
SDL_JOYAXISMOTION |
joystick axis motion |
SDL_JOYBALLMOTION |
joystick trackball motion |
SDL_JOYHATMOTION |
joystick hat position change |
SDL_JOYBUTTONDOWN |
joystick button pressed |
SDL_JOYBUTTONUP |
joystick button released |
SDL_JOYDEVICEADDED |
joystick connected |
SDL_JOYDEVICEREMOVED |
joystick disconnected |
Controller events |
|
SDL_CONTROLLERAXISMOTION |
controller axis motion |
SDL_CONTROLLERBUTTONDOWN |
controller button pressed |
SDL_CONTROLLERBUTTONUP |
controller button released |
SDL_CONTROLLERDEVICEADDED |
controller connected |
SDL_CONTROLLERDEVICEREMOVED |
controller disconnected |
SDL_CONTROLLERDEVICEREMAPPED |
controller mapping updated |
Touch events |
|
SDL_FINGERDOWN |
|
SDL_FINGERUP |
|
SDL_FINGERMOTION |
|
Gesture events |
|
SDL_DOLLARGESTURE |
|
SDL_DOLLARRECORD |
|
SDL_MULTIGESTURE |
|
Clipboard events |
|
SDL_CLIPBOARDUPDATE |
the clipboard changed |
Drag and drop events |
|
SDL_DROPFILE |
the system requests a file open |
These are for your use, and should be allocated with SDL_RegisterEvents() |
|
SDL_USEREVENT |
a user-specified event |
SDL_LASTEVENT |
only for bounding internal arrays |
Code Examples
You can add your code example here
Remarks
Application Events
An SDL_QUIT event is generated when the user tries to close the last remaining SDL_Window. If it is ignored or filtered out, the window will remain open. If it is not ignored or filtered, it is queued normally and the window is allowed to close. When the window is closed, screen updates will complete, but have no effect.
On Mac OS X, pressing Command-Q (the standard keyboard shortcut for "Quit this application") will cause SDL to generate an SDL_QUIT event. The application is still responsible for terminating itself, however.
SDL_Init() installs signal handlers for SIGINT (keyboard interrupt) and SIGTERM (system termination request), if handlers do not already exist, that generate SDL_QUIT events as well. There is no way to determine the cause of an SDL_QUIT event, but setting a signal handler in your application will override the default generation of quit events for that signal.
Related Structures
