|
Size: 2133
Comment: add note about limitations (per Sam)
|
Size: 2192
Comment: minor change
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 28: | Line 28: |
| ''NOTE'': You should not expect to be able to create a window, render, or receive events on any thread other than the main one. For platform-specific exceptions or complicated options ask on the [[http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org|mailing list]]. | ''NOTE'': You should not expect to be able to create a window, render, or receive events on any thread other than the main one. For platform-specific exceptions or complicated options ask on the [[http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org|mailing list]] or [[http://forums.libsdl.org/viewtopic.php?t=5973|forum]]. |
DRAFT |
Thread Management
Include File(s): SDL_thread.h, SDL_mutex.h (contains thread synchronization primitives)
Introduction
The SDL thread structure is defined in SDL_thread.c.
typedef struct SDL_Thread SDL_Thread;
We compile SDL into a DLL. This means that it's the DLL which creates a new thread for the calling process with the SDL_CreateThread() API. There is a problem with this, that only the RTL of the SDL.DLL will be initialized for those threads, and not the RTL of the calling application!
To solve this, we make a little hack here. green
We'll always use the caller's _beginthread() and _endthread() APIs to start a new thread. This way, if it's the SDL.DLL which uses this API, then the RTL of SDL.DLL will be used to create the new thread, and if it's the application, then the RTL of the application will be used.
So, in short: Always use the _beginthread() and _endthread() of the calling runtime library!
green
NOTE: You should not expect to be able to create a window, render, or receive events on any thread other than the main one. For platform-specific exceptions or complicated options ask on the mailing list or forum.
Enumerations
