|
Size: 540
Comment: create page, add content (Rev 5540)
|
Size: 1435
Comment: update content - event remarks re: union (for consistency); camelcase
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| #pragma disable-camelcase | #pragma camelcase off |
| Line 11: | Line 11: |
| ||Uint8||'''type'''||SDL_QUIT|| | ||Uint32||'''type'''||SDL_QUIT|| |
| Line 19: | Line 19: |
| ''You can add useful comments here'' | *<<BR>>[[SDL_QuitEvent]] is a member of the [[SDL_Event]] union and is used when an event of type SDL_QUIT is reported. ^You would access it through the event's `quit` field.^ ,,As can be seen, ,,the [[SDL_QuitEvent]] structure serves no useful purpose ^itself^. The event ,,itself,, ^it describes/defines/contains???^, on the other hand, is very important. If you filter out or ignore a quit event then it is impossible for the user to close the window. On the other hand, if you do accept a quit event then the application window will be closed, and screen updates will still report success even though the application will no longer be visible. Note: The macro SDL_QuitRequested will return non-zero if a quit event is pending. <<BR>>* <<Color2(green,SDL_QuitRequested seems to be a define in quit.h. Don't see it as a macro.)>> |
| Line 22: | Line 25: |
| .[[SDL_EventMask]]??? .[[SDL_EventType]]??? |
.[[SDL_EventMask]] ??? .[[SDL_EventType]] ??? == Related Structures == .[[SDL_Event]] |
| Line 26: | Line 32: |
| .[[SDL_SetEventFilter]] * | |
| Line 28: | Line 35: |
| [[CategoryStruct]] | [[CategoryStruct]], [[CategoryEvents]] |
DRAFT |
SDL_QuitEvent
A structure that contains the "quit requested" event.
Contents
Data Fields
Uint32 |
type |
SDL_QUIT |
Code Examples
You can add your code example here
Remarks
*
SDL_QuitEvent is a member of the SDL_Event union and is used when an event of type SDL_QUIT is reported. You would access it through the event's `quit` field.
As can be seen, the SDL_QuitEvent structure serves no useful purpose itself. The event itself it describes/defines/contains???, on the other hand, is very important. If you filter out or ignore a quit event then it is impossible for the user to close the window. On the other hand, if you do accept a quit event then the application window will be closed, and screen updates will still report success even though the application will no longer be visible.
Note: The macro SDL_QuitRequested will return non-zero if a quit event is pending.
* green
Related Enumerations
SDL_EventMask ???
SDL_EventType ???
Related Structures
