Mercurial > sdl-ios-xcode
annotate docs/man3/SDL_keysym.3 @ 934:af585d6efec8
Date: Thu, 17 Jun 2004 11:38:51 -0700 (PDT)
From: Eric Wing <ewing2121@yahoo.com>
Subject: New OS X patch (was Re: [SDL] Bug with inverted mouse coordinates in
I have a new patch for OS X I would like to submit.
First, it appears no further action has been taken on
my fix from Apple on the OpenGL windowed mode mouse
inversion problem. The fix would reunify the code, and
no longer require case checking for which version of
the OS you are running. This is probably a good fix
because the behavior with the old code could change
again with future versions of the OS, so those fixes
are included in this new patch.
But in addition, when I was at Apple, I asked them
about the ability to distinguish between the modifier
keys on the left and right sides of the keyboard (e.g.
Left Shift, Right Shift, Left/Right Alt, L/R Cmd, L/R
Ctrl). They told me that starting with Panther, the OS
began supporting this feature. This has always been a
source of annoyance for me when bringing a program
that comes from Windows or Linux to OS X when the
keybindings happened to need distinguishable left-side
and right-side keys. So the rest of the patch I am
submitting contains new code to support this feature
on Panther (and presumably later versions of the OS).
So after removing the OS version checks for the mouse
inversion problem, I reused the OS version checks to
activate the Left/Right detection of modifier keys. If
you are running Panther (or above), the new code will
attempt to distinguish between sides. For the older
OS's, the code path reverts to the original code.
I've tested with Panther on a G4 Cube, G5 dual
processor, and Powerbook Rev C. The Cube and G5
keyboards demonstrated the ability to distinguish
between sides. The Powerbook seems to only have
left-side keys, but the patch was still able to handle
it by producing the same results as before the patch.
I also wanted to test a non-Apple keyboard.
Unfortunately, I don't have any PC USB keyboards.
However, I was able to borrow a Sun Microsystems USB
keyboard, so I tried that out on the G5, and I got the
correct behavior for left and right sides. I'm
expecting that if it worked with a Sun keyboard, most
other keyboards should work with no problems.
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Fri, 20 Aug 2004 22:35:23 +0000 |
| parents | e5bc29de3f0a |
| children | 546f7c1eb755 |
| rev | line source |
|---|---|
|
181
e5bc29de3f0a
Updated from the SDL Documentation Project
Sam Lantinga <slouken@libsdl.org>
parents:
55
diff
changeset
|
1 .TH "SDL_keysym" "3" "Tue 11 Sep 2001, 23:00" "SDL" "SDL API Reference" |
| 0 | 2 .SH "NAME" |
| 3 SDL_keysym\- Keysym structure | |
| 4 .SH "STRUCTURE DEFINITION" | |
| 5 .PP | |
| 6 .nf | |
| 7 \f(CWtypedef struct{ | |
| 8 Uint8 scancode; | |
| 9 SDLKey sym; | |
| 10 SDLMod mod; | |
| 11 Uint16 unicode; | |
| 12 } SDL_keysym;\fR | |
| 13 .fi | |
| 14 .PP | |
| 15 .SH "STRUCTURE DATA" | |
| 16 .TP 20 | |
| 17 \fBscancode\fR | |
| 18 Hardware specific scancode | |
| 19 .TP 20 | |
| 20 \fBsym\fR | |
| 21 SDL virtual keysym | |
| 22 .TP 20 | |
| 23 \fBmod\fR | |
| 24 Current key modifiers | |
| 25 .TP 20 | |
| 26 \fBunicode\fR | |
| 27 Translated character | |
| 28 .SH "DESCRIPTION" | |
| 29 .PP | |
| 30 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\&. | |
| 31 .PP | |
| 32 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: | |
| 33 .PP | |
| 34 .nf | |
| 35 \f(CW\&. | |
| 36 \&. | |
| 37 while(SDL_PollEvent(&event)){ | |
| 38 switch(event\&.type){ | |
| 39 case SDL_KEYDOWN: | |
| 40 if(event\&.key\&.keysym\&.sym==SDLK_LEFT) | |
| 41 move_left(); | |
| 42 break; | |
| 43 \&. | |
| 44 \&. | |
| 45 \&. | |
| 46 } | |
| 47 } | |
| 48 \&. | |
| 49 \&.\fR | |
| 50 .fi | |
| 51 .PP | |
| 52 \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: | |
| 53 .PP | |
| 54 .nf | |
| 55 \f(CWchar ch; | |
| 56 if ( (keysym\&.unicode & 0xFF80) == 0 ) { | |
| 57 ch = keysym\&.unicode & 0x7F; | |
| 58 } | |
| 59 else { | |
| 60 printf("An International Character\&. | |
| 61 "); | |
| 62 }\fR | |
| 63 .fi | |
| 64 .PP | |
| 65 UNICODE translation does have a slight overhead so don\&'t enable it unless its needed\&. | |
| 66 .SH "SEE ALSO" | |
| 67 .PP | |
| 68 \fI\fBSDLKey\fR\fR | |
|
181
e5bc29de3f0a
Updated from the SDL Documentation Project
Sam Lantinga <slouken@libsdl.org>
parents:
55
diff
changeset
|
69 ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:00 |