(2014-01-05 20:18)elisiano Wrote:I guess the problem is your custom script. It sounds like it just finishes after the 30 seconds instead of waiting for chrome to exist.(2014-01-05 08:34)CAJN Wrote:(2014-01-05 08:21)CAJN Wrote: Here is my advancedsettings.xml:
<timeseekforward>10</timeseekforward> <!-- Time to seek forward in seconds when doing a short seek. Defaults to 30. -->
And to answer your other questions, I do have it set to go directly into XBMC via XBMCLauncher and yes the desktop is running (windows 7 Pro).
Thank you for your response.
Ok, an update for any that may experience this issue. Within XBMCLauncher there is a setting that you need to untick (Permanently disable re-focus), as the Launcher will attempt to refocus XBMC every 10 seconds if you don't.
Props to the author of this thread to pointing me in the right direction, tyvm and what a well done plug-in.
I have the same issue on Linux (using XBMCBuntu).
I made a script as suggested launching openbox and waiting for the pids of chrome to exit but XBMC regains focus after 30 seconds (exactly the delay before collecting the pids).
Does anyone else have the same issue?
I will try to change this whole custom script thing, so that it will be handled some other way.
As a dirty workaround, could you just start openbox in you script and leave it running? Just to make sure this is the problem...