[badaas]

This is a bit of a nuisance, as a lot of settings get, erm.. set here

This would probably cut 50% of the bugs reported about skins, when the usual 'I rebooted kodi and it worked' scenario happens.

[jurialmunkey]

In DialogConfirm.xml put this:

Code:

<onunload condition="String.IsEmpty(Window(Home).Property(SkinStartup))">ActivateWindow(Startup.xml)</onunload>

And then in Startup.xml put this:

Code:

<onload>SetProperty(SkinStartup,1,Home)</onload>

[badaas]

In DialogConfirm.xml put this:

Code:

<onunload condition="String.IsEmpty(Window(Home).Property(SkinStartup))">ActivateWindow(Startup.xml)</onunload>

And then in Startup.xml put this:

Code:

<onload>SetProperty(SkinStartup,1,Home)</onload>

ahh, I already have this:

Code:

                        <onclick condition="String.IsEmpty(Window(home).Property(adonic_loaded))">ReplaceWindow(StartUp.xml)</onclick>

I *think* now I've posted this before (*embarassed*), and solved it oops.
What happened I loaded another skin, then went back to mine, but ofc. the prop is already set.

Something else to *hack* ...

thanks @jm

[jurialmunkey]

Ah I didn't realise that window properties stayed set even after switching skins. That is really interesting. Though I can't see how it would cause any problems as all the properties and scripts etc that you would launch on startup should already be set or running anyway then. Still, would be nice to be able to run a splash screen on skin switch.