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
..
Src	XInitThreads() must be the very first Xlib function called or else	2011-02-19 21:53:53 +00:00
CMakeLists.txt	Fix the cmake build.	2011-02-11 21:49:29 +00:00
Plugin_VideoOGL.vcxproj	windows: buildfix for non-release configs	2011-02-11 22:27:50 +00:00
Plugin_VideoOGL.vcxproj.filters	vs2010: small fixups to vcxproj files.	2011-02-04 23:12:29 +00:00