Mercurial > sdl-ios-xcode
view docs/man3/SDL_VideoInfo.3 @ 4168:69bcba65c388 SDL-1.2
Fixed bug #526
Comment #1 From Simon Howard 2009-03-20 16:50:56
Hi,
I'm the author of Chocolate Doom, one of the other source ports that James
mentioned. This is a patch against the current SVN version of SDL 1.2 that
fixes the bug. It has been tested and hopefully should be obviously correct
from examining the changes. I'll give a brief explanation.
When the palette is set with SDL_SetPalette, the IDirectDrawPalette_SetEntries
DirectX function is invoked. However, when this happens, a WM_PALETTECHANGED
message is sent to the window.
A WM_PALETTECHANGED message can also be received if the palette is changed for
some other reason, like if the system palette is changed. Therefore, the
palette change handler (DX5_PaletteChanged) has code to deal with this case.
It distinguishes "expected" palette changes (set with SDL_SetPalette) from
"unexpected" palette changes using the colorchange_expected variable, which is
set before calling IDirectDrawPalette_SetEntries. However, the code to set
this variable is missing in the fullscreen code path. By setting this
variable, the palette change is handled properly and the freezes go away.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Mon, 13 Apr 2009 00:53:12 +0000 |
parents | 4e3b250c950e |
children | 1238da4a7112 |
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