7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="SDL Library Documentation"
11 HREF="index.html"><LINK
13 TITLE="SDL Event Structures."
14 HREF="eventstructures.html"><LINK
17 HREF="sdlquitevent.html"><LINK
20 HREF="sdlkey.html"></HEAD
31 SUMMARY="Header navigation table"
40 >SDL Library Documentation</TH
48 HREF="sdlquitevent.html"
83 >SDL_keysym -- Keysym structure</DIV
90 >Structure Definition</H2
92 CLASS="PROGRAMLISTING"
108 CLASS="INFORMALTABLE"
131 >Hardware specific scancode</TD
146 >SDL virtual keysym</TD
161 >Current key modifiers</TD
176 >Translated character</TD
195 > structure is used by reporting key presses and releases since it is a part of the <A
196 HREF="sdlkeyboardevent.html"
199 >SDL_KeyboardEvent</SPAN
208 > field should generally be left alone, it is the hardware dependent scancode returned by the keyboard. The <TT
213 > field is extremely useful. It is the SDL-defined value of the key (see <A
216 >. This field is very useful when you are checking for certain key presses, like so:
218 CLASS="PROGRAMLISTING"
221 while(SDL_PollEvent(&event)){
224 if(event.key.keysym.sym==SDLK_LEFT)
240 > stores the current state of the keyboard modifiers as explained in <A
241 HREF="sdlgetmodstate.html"
251 > is only used when UNICODE translation is enabled with <A
252 HREF="sdlenableunicode.html"
255 >SDL_EnableUNICODE</TT
262 > is non-zero then this a the UNICODE character corresponding to the keypress. If the high 9 bits of the character are 0, then this maps to the equivalent ASCII character:
264 CLASS="PROGRAMLISTING"
266 if ( (keysym.unicode & 0xFF80) == 0 ) {
267 ch = keysym.unicode & 0x7F;
270 printf("An International Character.\n");
273 UNICODE translation does have a slight overhead so don't enable it unless its needed.</P
296 SUMMARY="Footer navigation table"
307 HREF="sdlquitevent.html"
341 HREF="eventstructures.html"