Mercurial > sdl-ios-xcode
view docs/man3/SDL_keysym.3 @ 1982:3b4ce57c6215
First shot at new audio data types (int32 and float32).
Notable changes:
- Converters between types are autogenerated. Instead of making multiple
passes over the data with seperate filters for endianess, size, signedness,
etc, converting between data types is always one specialized filter. This
simplifies SDL_BuildAudioCVT(), which otherwise had a million edge cases
with the new types, and makes the actually conversions more CPU cache
friendly. Left a stub for adding specific optimized versions of these
routines (SSE/MMX/Altivec, assembler, etc)
- Autogenerated converters are built by SDL/src/audio/sdlgenaudiocvt.pl. This
does not need to be run unless tweaking the code, and thus doesn't need
integration into the build system.
- Went through all the drivers and tried to weed out all the "Uint16"
references that are better specified with the new SDL_AudioFormat typedef.
- Cleaned out a bunch of hardcoded bitwise magic numbers and replaced them
with new SDL_AUDIO_* macros.
- Added initial float32 and int32 support code. Theoretically, existing
drivers will push these through converters to get the data they want to
feed to the hardware.
Still TODO:
- Optimize and debug new converters.
- Update the CoreAudio backend to accept float32 data directly.
- Other backends, too?
- SDL_LoadWAV() needs to be updated to support int32 and float32 .wav files
(both of which exist and can be generated by 'sox' for testing purposes).
- Update the mixer to handle new datatypes.
- Optionally update SDL_sound and SDL_mixer, etc.
| author | Ryan C. Gordon <icculus@icculus.org> |
|---|---|
| date | Thu, 24 Aug 2006 12:10:46 +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