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.

.TH "SDL_CreateMutex" "3" "Tue 11 Sep 2001, 23:00" "SDL" "SDL API Reference" 
.SH "NAME"
SDL_CreateMutex \- Create a mutex
.SH "SYNOPSIS"
.PP
\fB#include "SDL\&.h"
#include "SDL_thread\&.h"
.sp
\fBSDL_mutex *\fBSDL_CreateMutex\fP\fR(\fBvoid\fR);
.SH "DESCRIPTION"
.PP
Create a new, unlocked mutex\&.
.SH "EXAMPLES"
.PP
.nf
\f(CWSDL_mutex *mut;

mut=SDL_CreateMutex();
\&.
\&.
if(SDL_mutexP(mut)==-1){
  fprintf(stderr, "Couldn\&'t lock mutex
");
  exit(-1);
}
\&.
/* Do stuff while mutex is locked */
\&.
\&.
if(SDL_mutexV(mut)==-1){
  fprintf(stderr, "Couldn\&'t unlock mutex
");
  exit(-1);
}

SDL_DestroyMutex(mut);
\fR
.fi
.PP
.SH "SEE ALSO"
.PP
\fI\fBSDL_mutexP\fP\fR, \fI\fBSDL_mutexV\fP\fR, \fI\fBSDL_DestroyMutex\fP\fR
...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:00