Mercurial > sdl-ios-xcode
view docs/man3/SDL_keysym.3 @ 1768:814f9f2c7a33
Fixed bug #80
Date: 21 Apr 2003 17:20:20 +0100
From: Alan Swanson <swanson@uklinux.net>
Subject: [SDL] New XFree 4.3 Video Mode Patch
If you look at the unsorted list of modes returned by X, here's mine;
1280 x 1024 @ 85.0 >
1024 x 768 @ 100.3 > USER
800 x 600 @ 125.5 > SET
640 x 480 @ 124.9 >
1280 x 1024 @ 75.0 ]
1280 x 1024 @ 60.0 ]
1280 x 960 @ 85.0 ] X11
1280 x 960 @ 60.0 ] AUTO
1152 x 864 @ 75.0 ]=20
1152 x 768 @ 54.8 ]
960 x 720 @ 120.0 ]
...
640 x 400 @ 85.1 ] 256k
576 x 432 @ 150.0 ] 249k PIXEL
640 x 350 @ 85.1 ] 224k COUNT
576 x 384 @ 109.6 ] 221k
...
The user set modes come first followed by X set modes which are ordered
by decreasing number of pixels and refresh.
The reason why every other library or program not using SDL working is
due to SDL scanning the modes in reverse getting X11 provided modes
modes with the lowest refresh.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Fri, 05 May 2006 05:50:26 +0000 |
parents | e5bc29de3f0a |
children | 546f7c1eb755 |
line wrap: on
line source
.TH "SDL_keysym" "3" "Tue 11 Sep 2001, 23:00" "SDL" "SDL API Reference" .SH "NAME" SDL_keysym\- Keysym structure .SH "STRUCTURE DEFINITION" .PP .nf \f(CWtypedef struct{ Uint8 scancode; SDLKey sym; SDLMod mod; Uint16 unicode; } SDL_keysym;\fR .fi .PP .SH "STRUCTURE DATA" .TP 20 \fBscancode\fR Hardware specific scancode .TP 20 \fBsym\fR SDL virtual keysym .TP 20 \fBmod\fR Current key modifiers .TP 20 \fBunicode\fR Translated character .SH "DESCRIPTION" .PP The \fBSDL_keysym\fR structure is used by reporting key presses and releases since it is a part of the \fI\fBSDL_KeyboardEvent\fR\fR\&. .PP The \fBscancode\fR field should generally be left alone, it is the hardware dependent scancode returned by the keyboard\&. The \fBsym\fR field is extremely useful\&. It is the SDL-defined value of the key (see \fISDL Key Syms\fR\&. This field is very useful when you are checking for certain key presses, like so: .PP .nf \f(CW\&. \&. while(SDL_PollEvent(&event)){ switch(event\&.type){ case SDL_KEYDOWN: if(event\&.key\&.keysym\&.sym==SDLK_LEFT) move_left(); break; \&. \&. \&. } } \&. \&.\fR .fi .PP \fBmod\fR stores the current state of the keyboard modifiers as explained in \fI\fBSDL_GetModState\fP\fR\&. The \fBunicode\fR is only used when UNICODE translation is enabled with \fI\fBSDL_EnableUNICODE\fP\fR\&. If \fBunicode\fR 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: .PP .nf \f(CWchar ch; if ( (keysym\&.unicode & 0xFF80) == 0 ) { ch = keysym\&.unicode & 0x7F; } else { printf("An International Character\&. "); }\fR .fi .PP UNICODE translation does have a slight overhead so don\&'t enable it unless its needed\&. .SH "SEE ALSO" .PP \fI\fBSDLKey\fR\fR ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:00