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
..
resources	Merge UI related projects into the main DolphinWX project.	2011-02-11 21:37:52 +00:00
Src	XInitThreads() must be the very first Xlib function called or else	2011-02-19 21:53:53 +00:00
CMakeLists.txt	Move the log window options from the log window into a separate dialog openned from an item in the options menu. This gives the log window room to show logs.	2011-02-18 12:34:24 +00:00
Dolphin.vcxproj	Move the log window options from the log window into a separate dialog openned from an item in the options menu. This gives the log window room to show logs.	2011-02-18 12:34:24 +00:00
Dolphin.vcxproj.filters	Move the log window options from the log window into a separate dialog openned from an item in the options menu. This gives the log window room to show logs.	2011-02-18 12:34:24 +00:00
Dolphin.vcxproj.user	vs2010:	2011-01-31 15:53:54 +00:00
DolphinWX.rc	Hg:	2010-06-09 01:37:08 +00:00
resource.h	set svn:eol-style=native for **.h	2008-12-08 04:46:09 +00:00