[rob hodge]

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 guess the problem is your custom script. It sounds like it just finishes after the 30 seconds instead of waiting for chrome to exist.
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...

funny, that script works perfectly in on mine. i may have decreased the wait and risked the race condition a bit more. regardless, perhaps yo uaren;t getting the correct PID to pass to wait? if you're using chrome instead of chromium or vice-versa in the script, (or a typo, etc) you'll run wait with no PID and it will just move onto the next command, and kill openbox.

one thing yo might want to do is try echoing the PIDS PIDOF is getting to a file to verify you are getting the numbers you need.

regardless; passing the chromium launch command in quotes as a variable to the custom script would make things so much easier; one could setup and tear down things like remote control configs, window manager, etc very easily.