Mercurial > sdl-ios-xcode
view 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 |
line wrap: on
line source
.TH "SDL_VideoInfo" "3" "Tue 11 Sep 2001, 23:01" "SDL" "SDL API Reference" .SH "NAME" SDL_VideoInfo\- Video Target information .SH "STRUCTURE DEFINITION" .PP .nf \f(CWtypedef struct{ Uint32 hw_available:1; Uint32 wm_available:1; Uint32 blit_hw:1; Uint32 blit_hw_CC:1; Uint32 blit_hw_A:1; Uint32 blit_sw:1; Uint32 blit_sw_CC:1; Uint32 blit_sw_A:1; Uint32 blit_fill; Uint32 video_mem; SDL_PixelFormat *vfmt; } SDL_VideoInfo;\fR .fi .PP .SH "STRUCTURE DATA" .TP 20 \fBhw_available\fR Is it possible to create hardware surfaces? .TP 20 \fBwm_available\fR Is there a window manager available .TP 20 \fBblit_hw\fR Are hardware to hardware blits accelerated? .TP 20 \fBblit_hw_CC\fR Are hardware to hardware colorkey blits accelerated? .TP 20 \fBblit_hw_A\fR Are hardware to hardware alpha blits accelerated? .TP 20 \fBblit_sw\fR Are software to hardware blits accelerated? .TP 20 \fBblit_sw_CC\fR Are software to hardware colorkey blits accelerated? .TP 20 \fBblit_sw_A\fR Are software to hardware alpha blits accelerated? .TP 20 \fBblit_fill\fR Are color fills accelerated? .TP 20 \fBvideo_mem\fR Total amount of video memory in Kilobytes .TP 20 \fBvfmt\fR \fIPixel format\fR of the video device .SH "DESCRIPTION" .PP 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\&. .SH "SEE ALSO" .PP \fI\fBSDL_PixelFormat\fR\fR, \fI\fBSDL_GetVideoInfo\fP\fR ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:01