Annotated edit history of
SDL_PushEvent(3) version 2 showing authors affecting page license.
View with all changes included.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
SDL_!PushEvent |
| |
|
2 |
!!!SDL_!PushEvent |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
RETURN VALUE |
| |
|
7 |
EXAMPLES |
| |
|
8 |
SEE ALSO |
| |
|
9 |
---- |
| |
|
10 |
!!NAME |
| |
|
11 |
|
| |
|
12 |
|
| |
|
13 |
SDL_!PushEvent- Pushes an event onto the event queue |
| |
|
14 |
!!SYNOPSIS |
| |
|
15 |
|
| |
|
16 |
|
| |
|
17 |
__#include __ |
| |
|
18 |
|
| |
|
19 |
|
| |
|
20 |
__int SDL_!PushEvent__(__SDL_Event |
| |
|
21 |
*event__); |
| |
|
22 |
!!DESCRIPTION |
| |
|
23 |
|
| |
|
24 |
|
| |
|
25 |
The event queue can actually be used as a two way |
| |
|
26 |
communication channel. Not only can events be read from the |
| |
|
27 |
queue, but the user can also push their own events onto it. |
| |
|
28 |
__event__ is a pointer to the event structure you wish to |
| |
|
29 |
push onto the queue. |
| |
|
30 |
|
| |
|
31 |
|
| |
|
32 |
__Note:__ |
| |
|
33 |
|
| |
|
34 |
|
| |
|
35 |
Pushing device input events onto the queue doesn't modify |
| |
|
36 |
the state of the device within SDL. |
| |
|
37 |
!!RETURN VALUE |
| |
|
38 |
|
| |
|
39 |
|
| |
|
40 |
Returns __0__ on success or __-1__ if the event |
| |
|
41 |
couldn't be pushed. |
| |
|
42 |
!!EXAMPLES |
| |
|
43 |
|
| |
|
44 |
|
| |
|
45 |
See __SDL_Event__. |
| |
|
46 |
!!SEE ALSO |
| |
|
47 |
|
| |
|
48 |
|
| |
|
49 |
__SDL_!PollEvent__, __SDL_!PeepEvents__, |
| |
|
50 |
__SDL_Event__ |
| |
|
51 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
