2014-07-09, 14:31
If thats the case then there is probably something going on with the Window or database path that is changing with the Profile.
I dont think there is anything I can do. There is no way that I can see that a change in Profile can be detected and the service immediately interrupted and disabled and then re-enabled.
A work-around for you may be to add "xbmc.sleep(60000)" somewhere near the top of the service.py (immediately below the "import xbmc" line would be best). That will have the service wait 60 seconds before progressing, giving you enough time to change the Profile.
I dont think there is anything I can do. There is no way that I can see that a change in Profile can be detected and the service immediately interrupted and disabled and then re-enabled.
A work-around for you may be to add "xbmc.sleep(60000)" somewhere near the top of the service.py (immediately below the "import xbmc" line would be best). That will have the service wait 60 seconds before progressing, giving you enough time to change the Profile.