Wiki Page Content

Differences between revisions 1 and 2
Revision 1 as of 2011-05-10 21:55:18
Size: 1170
Editor: SheenaSmith
Comment: create page - 4/22 cd2167525827
Revision 2 as of 2011-06-12 16:24:35
Size: 547
Editor: SheenaSmith
Comment: update content - w/ Sam; remove draft
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
||<tablewidth="100%" style="color: #FF0000;" :> DRAFT||
Line 6: Line 5:
Use this function to ^request/process a quit event ???^. Use this function to see whether an SLD_QUIT event is queued.
Line 12: Line 11:
void SDL_QuitRequested(void) SDL_bool SDL_QuitRequested(void)
Line 14: Line 13:

== Return Value ==
Returns SDL_TRUE if it is queued or SDL_FALSE otherwise.
Line 21: Line 23:
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.

[[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.
''You can add useful comments here''

SDL_QuitRequested

Use this function to see whether an SLD_QUIT event is queued.

Syntax

SDL_bool SDL_QuitRequested(void)

Return Value

Returns SDL_TRUE if it is queued or SDL_FALSE otherwise.

Code Examples

You can add your code example here

Remarks

You can add useful comments here


CategoryAPI, CategoryEvents

None: SDL_QuitRequested (last edited 2015-04-26 19:08:07 by PhilippWiesemann)

(Page Info.)
Feedback
Please include your contact information if you'd like to receive a reply.
Submit