2018-04-25, 01:12
I think this is a bug?
Tested on win 7x64 with Kodi 18 nightly Winx64 master 180422
Created a profile. No locks / separate sources / fresh settings
Installed Aeon Nox 5 from Kodi repo
Set Aeon Nox 5 as the skin for the new profile.
When I log off master (skin Estuary) and go into loginscreen then select the new profile. From looking at the log and observing behavior, as the new profile gets initialized the startup window (startup.xml) from Estuary gets loaded and then home window (home.xml) also from Estuary and only after that is the new skin (Aeon Nox) loaded. So the stuff that needs to run from startup never runs.
The same thing happens in reverse when logging off the new profile and going back to master profile.
Stuff running (or not running) from "onload" statements in startup.xml and home.xml causes problems.
ISTM the new skin should first be loaded, then initialize the new skin and get the appropriate startup window for the new skin.
scott s.
.
Tested on win 7x64 with Kodi 18 nightly Winx64 master 180422
Created a profile. No locks / separate sources / fresh settings
Installed Aeon Nox 5 from Kodi repo
Set Aeon Nox 5 as the skin for the new profile.
When I log off master (skin Estuary) and go into loginscreen then select the new profile. From looking at the log and observing behavior, as the new profile gets initialized the startup window (startup.xml) from Estuary gets loaded and then home window (home.xml) also from Estuary and only after that is the new skin (Aeon Nox) loaded. So the stuff that needs to run from startup never runs.
The same thing happens in reverse when logging off the new profile and going back to master profile.
Stuff running (or not running) from "onload" statements in startup.xml and home.xml causes problems.
ISTM the new skin should first be loaded, then initialize the new skin and get the appropriate startup window for the new skin.
scott s.
.
