Mercurial > sdl-ios-xcode
annotate docs/man3/SDL_VideoInfo.3 @ 2268:4baee598306d
Date: Thu, 05 Jul 2007 14:02:33 -0700
From: Sam Lantinga
Subject: SDL 1.3 keyboard plan
After lots of discussion with Christian, this is what we came up with:
> So, to sum up...
> SDLK_* become the physical keys, starting at > (1<<21)
> We create a macro SDLK_INDEX(X)
> We have two functions SDL_GetLayoutKey(SDLKey) and SDL_GetKeyName()
> SDL_GetLayoutKey maps to UCS4 for printable characters, and SDLK* for
non-printable characters
> and does so based on the OS's current keyboard layout
> SDL_GetKeyName() handles both SDLK_* and UCS4, converting UCS4 to UTF-8 and
converting SDLK_* into our names, which are UTF-8 for printable characters.
> WASD folks use SDLK_*, and 'I' folks use SDL_GetLayoutKey(SDLK_*)
Here is the patch he came up with, and his e-mail about it:
Date: Fri, 17 Aug 2007 19:50:28 +0200
From: Christian Walther
Subject: Re: SDL 1.3 keyboard plan
> Sounds great, go ahead and send me a patch.
Here goes! Thanks for having a look. Don't hesitate to comment if
anything does not conform to your ideas.
One caveat: Committing this now may break compilability of some video
drivers - specifically, if they use any of the SDLK_* codes that were
obsoleted and moved into SDL_compat.h. I only tried Cocoa (which did
break, but is already fixed) and X11 (which didn't, but then its key
handling is #iffed out). If that's a problem, it may need to go into
a branch.
-Christian
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Sun, 19 Aug 2007 14:52:52 +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_VideoInfo" "3" "Tue 11 Sep 2001, 23:01" "SDL" "SDL API Reference" |
| 0 | 2 .SH "NAME" |
| 3 SDL_VideoInfo\- Video Target information | |
| 4 .SH "STRUCTURE DEFINITION" | |
| 5 .PP | |
| 6 .nf | |
| 7 \f(CWtypedef struct{ | |
| 8 Uint32 hw_available:1; | |
| 9 Uint32 wm_available:1; | |
| 10 Uint32 blit_hw:1; | |
| 11 Uint32 blit_hw_CC:1; | |
| 12 Uint32 blit_hw_A:1; | |
| 13 Uint32 blit_sw:1; | |
| 14 Uint32 blit_sw_CC:1; | |
| 15 Uint32 blit_sw_A:1; | |
| 16 Uint32 blit_fill; | |
| 17 Uint32 video_mem; | |
| 18 SDL_PixelFormat *vfmt; | |
| 19 } SDL_VideoInfo;\fR | |
| 20 .fi | |
| 21 .PP | |
| 22 .SH "STRUCTURE DATA" | |
| 23 .TP 20 | |
| 24 \fBhw_available\fR | |
| 25 Is it possible to create hardware surfaces? | |
| 26 .TP 20 | |
| 27 \fBwm_available\fR | |
| 28 Is there a window manager available | |
| 29 .TP 20 | |
| 30 \fBblit_hw\fR | |
| 31 Are hardware to hardware blits accelerated? | |
| 32 .TP 20 | |
| 33 \fBblit_hw_CC\fR | |
| 34 Are hardware to hardware colorkey blits accelerated? | |
| 35 .TP 20 | |
| 36 \fBblit_hw_A\fR | |
| 37 Are hardware to hardware alpha blits accelerated? | |
| 38 .TP 20 | |
| 39 \fBblit_sw\fR | |
| 40 Are software to hardware blits accelerated? | |
| 41 .TP 20 | |
| 42 \fBblit_sw_CC\fR | |
| 43 Are software to hardware colorkey blits accelerated? | |
| 44 .TP 20 | |
| 45 \fBblit_sw_A\fR | |
| 46 Are software to hardware alpha blits accelerated? | |
| 47 .TP 20 | |
| 48 \fBblit_fill\fR | |
| 49 Are color fills accelerated? | |
| 50 .TP 20 | |
| 51 \fBvideo_mem\fR | |
| 52 Total amount of video memory in Kilobytes | |
| 53 .TP 20 | |
| 54 \fBvfmt\fR | |
| 55 \fIPixel format\fR of the video device | |
| 56 .SH "DESCRIPTION" | |
| 57 .PP | |
| 58 This (read-only) structure is returned by \fI\fBSDL_GetVideoInfo\fP\fR\&. It contains information on either the \&'best\&' available mode (if called before \fI\fBSDL_SetVideoMode\fP\fR) or the current video mode\&. | |
| 59 .SH "SEE ALSO" | |
| 60 .PP | |
| 61 \fI\fBSDL_PixelFormat\fR\fR, \fI\fBSDL_GetVideoInfo\fP\fR | |
|
181
e5bc29de3f0a
Updated from the SDL Documentation Project
Sam Lantinga <slouken@libsdl.org>
parents:
55
diff
changeset
|
62 ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:01 |