Soren Jorvang d2910912a4 XInitThreads() must be the very first Xlib function called or else ... some X state will have initialized mutexes and some won't, leading to unpredictable results depending on the feature set compiled into wxWidgets and so on. wxGTK starts by calling Xlib functions indirectly through gdk very early on, so we must hook into wxApp::Initialize(). I believe this should properly fix issue 1540. In case of problems, please reopen that issue. If you see XLockMutex in a backtrace, that's a pretty good indication. git-svn-id: https://dolphin-emu.googlecode.com/svn/trunk@7205 8ced0084-cf51-0410-be5f-012b33b47a6e		2011-02-19 21:53:53 +00:00
..
AudioCommon	Some work on changing comments, log messages, and variable and function names to reflect that the plugins are not plugins anymore.	2011-02-14 02:18:03 +00:00
Common	Core/Common: Add support for low 8 bit parts of SI,DI,BP on 64 bit in x64Emitter	2011-02-19 14:20:52 +00:00
Core	setup ios revision (makes some wii demos shutup)	2011-02-19 21:40:03 +00:00
DiscIO	drop vs2008 projects in favor of vs2010	2011-02-11 15:43:05 +00:00
DolphinWX	XInitThreads() must be the very first Xlib function called or else	2011-02-19 21:53:53 +00:00
InputCommon	Build fixes when using SDL 1.3 related to force feedback support, as suggested in issue #1338.	2011-02-19 07:06:26 +00:00
VideoCommon	Call Video_Prepare() before starting the CPU thread.	2011-02-18 23:52:14 +00:00
CMakeLists.txt	Merge UI related projects into the main DolphinWX project.	2011-02-11 21:37:52 +00:00