Mercurial > sdl-ios-xcode

comparison docs/html/sdlpushevent.html @ 55:55f1f1b3e27d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added new docs for SDL 1.2.1
author Sam Lantinga <slouken@lokigames.com>
date Sun, 10 Jun 2001 19:31:57 +0000
parents 74212992fb08
children e5bc29de3f0a
comparison
equal deleted inserted replaced
54:028447a8a758 55:55f1f1b3e27d
2 ><HEAD 2 ><HEAD
3 ><TITLE 3 ><TITLE
4 >SDL_PushEvent</TITLE 4 >SDL_PushEvent</TITLE
5 ><META 5 ><META
6 NAME="GENERATOR" 6 NAME="GENERATOR"
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.61 7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
8 "><LINK 8 "><LINK
9 REL="HOME" 9 REL="HOME"
10 TITLE="SDL Library Documentation" 10 TITLE="SDL Library Documentation"
11 HREF="index.html"><LINK 11 HREF="index.html"><LINK
12 REL="UP" 12 REL="UP"
71 >SDL_PushEvent</A 71 >SDL_PushEvent</A
72 ></H1 72 ></H1
73 ><DIV 73 ><DIV
74 CLASS="REFNAMEDIV" 74 CLASS="REFNAMEDIV"
75 ><A 75 ><A
76 NAME="AEN4918" 76 NAME="AEN4993"
77 ></A 77 ></A
78 ><H2 78 ><H2
79 >Name</H2 79 >Name</H2
80 >SDL_PushEvent&nbsp;--&nbsp;Pushes an event onto the event queue</DIV 80 >SDL_PushEvent&nbsp;--&nbsp;Pushes an event onto the event queue</DIV
81 ><DIV 81 ><DIV
82 CLASS="REFSYNOPSISDIV" 82 CLASS="REFSYNOPSISDIV"
83 ><A 83 ><A
84 NAME="AEN4921" 84 NAME="AEN4996"
85 ></A 85 ></A
86 ><H2 86 ><H2
87 >Synopsis</H2 87 >Synopsis</H2
88 ><DIV 88 ><DIV
89 CLASS="FUNCSYNOPSIS" 89 CLASS="FUNCSYNOPSIS"
90 ><A 90 ><A
91 NAME="AEN4922" 91 NAME="AEN4997"
92 ></A 92 ></A
93 ><P 93 ><P
94 ></P 94 ></P
95 ><PRE 95 ><PRE
96 CLASS="FUNCSYNOPSISINFO" 96 CLASS="FUNCSYNOPSISINFO"
110 ></DIV 110 ></DIV
111 ></DIV 111 ></DIV
112 ><DIV 112 ><DIV
113 CLASS="REFSECT1" 113 CLASS="REFSECT1"
114 ><A 114 ><A
115 NAME="AEN4928" 115 NAME="AEN5003"
116 ></A 116 ></A
117 ><H2 117 ><H2
118 >Description</H2 118 >Description</H2
119 ><P 119 ><P
120 >The event queue can actually be used as a two way communication channel. Not only can events be read from the queue, but the user can also push their own events onto it. <TT 120 >The event queue can actually be used as a two way communication channel. Not only can events be read from the queue, but the user can also push their own events onto it. <TT
135 ></DIV 135 ></DIV
136 ></DIV 136 ></DIV
137 ><DIV 137 ><DIV
138 CLASS="REFSECT1" 138 CLASS="REFSECT1"
139 ><A 139 ><A
140 NAME="AEN4934" 140 NAME="AEN5009"
141 ></A 141 ></A
142 ><H2 142 ><H2
143 >Return Value</H2 143 >Return Value</H2
144 ><P 144 ><P
145 >Returns <SPAN 145 >Returns <SPAN
151 > if the event couldn't be pushed.</P 151 > if the event couldn't be pushed.</P
152 ></DIV 152 ></DIV
153 ><DIV 153 ><DIV
154 CLASS="REFSECT1" 154 CLASS="REFSECT1"
155 ><A 155 ><A
156 NAME="AEN4939" 156 NAME="AEN5014"
157 ></A 157 ></A
158 ><H2 158 ><H2
159 >Examples</H2 159 >Examples</H2
160 ><P 160 ><P
161 >See <A 161 >See <A
167 >.</P 167 >.</P
168 ></DIV 168 ></DIV
169 ><DIV 169 ><DIV
170 CLASS="REFSECT1" 170 CLASS="REFSECT1"
171 ><A 171 ><A
172 NAME="AEN4944" 172 NAME="AEN5019"
173 ></A 173 ></A
174 ><H2 174 ><H2
175 >See Also</H2 175 >See Also</H2
176 ><P 176 ><P
177 ><A 177 ><A