2009-06-23, 08:34
Maybe it is because it says it is an sdl app before it says xbmc?!? and it only checks the xbmc?
/needtotest
/needtotest
2009-06-23, 13:27
What the heck did someone delete my post from last night? Yes, it is because the FindWindow doesn't match due to the name not being set. However, just looking for both doesn't help because the space between the check and the creation of the window is long enough that you can still launch multiple copies.
Really the only reliable way to do this in Win32 is with a null-security named mutex.
Really the only reliable way to do this in Win32 is with a null-security named mutex.
2009-07-07, 16:30
Just posted this request, maybe others are interested too
ticket... http://trac.xbmc.org/ticket/6870
ticket... http://trac.xbmc.org/ticket/6870
Quote:I'd like to see a default setting that XBMC.EXE checks to see if it is already loaded in memory before initializing another instance.
And an option, via cmd line switch, to allow multiple instance to load in case it is needed, for some future functionality like multi-screens, etc.
2009-07-07, 22:00
The interesting thing is that I cannot get it to load multiples on my own.
BUT when I'm using it in daily use, I use EventGhost to start XBMC... and often (once a day or more) it will start 2 or 3 instances.
BUT when I'm using it in daily use, I use EventGhost to start XBMC... and often (once a day or more) it will start 2 or 3 instances.
2009-07-07, 22:47
I can confirm this, with versions of XBMC dating back... I don't know. Six months at least? EventGhost key bound on the remote with just XBMC.exe, often leads to two instances running.
2009-07-08, 22:14
Looks like Wiso has recently fixed it using mutex for windows. Hence it is no longer an issue with windows.
