2011-12-09, 02:16
Martijn Wrote:That would run it each time you enter home am i right?
Maybe have it in startup.xml so it's started one time.
What if you use sleep instead of quit/shutdown on you htpc? I do.
Martijn Wrote:That would run it each time you enter home am i right?
Maybe have it in startup.xml so it's started one time.
<onload condition="IsEmpty(Window(Home).Property(Watchlist_Running))">RunScript(script.watchlist,movies=$INFO[Skin.String(Watchlist_Movies)]&episodes=$INFO[Skin.String(Watchlist_Episodes)]&albums=$INFO[Skin.String(Watchlist_Albums)]&limit=6)</onload>
Hitcher Wrote:Now that ronie's added the running property I run it from Startup.xml and then use a conditional for the Home.xml in case someone has switched skins..
PHP Code:<onload condition="IsEmpty(Window(Home).Property(Watchlist_Running))">RunScript(script.watchlist,movies=$INFO[Skin.String(Watchlist_Movies)]&episodes=$INFO[Skin.String(Watchlist_Episodes)]&albums=$INFO[Skin.String(Watchlist_Albums)]&limit=6)</onload>
pieh Wrote:If this script should be automaticly run consider using service addon. Not sure if we could enable/disable it from skin tho.
pecinko Wrote:Yup, but what do you think would be a solution for a situation were user is switching from a skin that uses say 4 items to a skin using 8. Or, from a skin not using music items in WL script to a skin that uses all.
All I came up with would be to run it on home.xml load to make sure all info would be fetched?
The way I see it you either re-run it on home with definable parameters or make a background service but with fixed parameters. I may be missing something, though?
Quote:<onload condition="IsEmpty(Window(Home).Property(Quartz_Watchlist))">RunScript(script.watchlist,...)</onload>
<onload condition="IsEmpty(Window(Home).Property(Quartz_Watchlist))">SetProperty(Quartz_Watchlist,True)</onload>
ronie Wrote:pieh, when a users switches skins, why don't we start the new skin from Startup.xml ?
currently, when changing skins, we skip everything the new skin has defined in Startup.xml and this leads to missing bits and pieces in the skin.
any thoughts?
pecinko Wrote:Maybe, but I've been told we are in feature freeze.
pecinko Wrote:Maybe, but I've been told we are in feature freeze.
pecinko Wrote:I still think there's no way of telling what parameters were used by previous skinindeed, and there's no need to.
pecinko Wrote:Even with property check ronie suggested - ones the property is set it will not guard from future skin switches.