[User 224999]

I like this, now i can starting to create "widget chooser" with this part of script.... Dont need shortcuts enymore....
This will work like view settings, right?

Yes, it's prettu much the same.

[Jayz2K]

Are you sure that the SetID winproperty is actually beiing set ?

Yup, made some more test and the Window prop shows correctly in a label.

Edit : The Prop is translated in the command. I removed a bracket and the log returned this :

Code:

00:34:20 T:7844   ERROR: Keymapping error: no such action 'runscript(script.skin.helper.service,action=setskinsetting,setting=vdo.view1.bbshow,header=vdo.view1.bbshow' defined

When setting the Prop in header tag, it shows correctly in the select dialog. So $INFO[Window(Home).Property(SetID)] = VDO.View1.BBShow.
Seems the problem comes from using the Prop in settings.xlm id="$INFO[Window(Home).Property(SetID)] " ...

Using the Prop value directly as id :

id="VDO.View1.BBShow" also works.
So the Window.Property is not resolved in settings.xml.

Maybe because the file is outside the 16x9 skin folder ?

[tomer953]

[quote='marcelveldt' pid='2213503' dateline='1452684069']

Code:

08:07:19 T:420   ERROR: Skin Helper Service --> Error while processing smart shortcuts for favourites - set disabled....

I think it's from CustomPicturesBackgroundPath

Should now be fixed on Git

amm, no errors now, but the "CustomPicturesBackgroundPath" is not affecting the backgrounds. even not the single rotating bg..
I also checked it on Titan, and also there the custom path is not working for me.

[badaas]

There seems to be a serious 2-3 second lag with latest versions of helper and emby plugin (at least). The lag affects all screens updates afai can tell.
This version 1.0.23 [ https://github.com/marcelveldt/script.sk...719e67799f ] works fine (in Titan & Eunique).
I havent tested past this version to determine where the lag was actually introduced..

The delay time seems to match the delay when info isn't cached, ie. on first entry to item.

[User 224999]

Seems the problem comes from using the Prop in settings.xlm id="$INFO[Window(Home).Property(SetID)] " ...

Now I get what you mean. You also want to use a infolabel for the ID itself in the skinsettings.xml
I have just adjusted this. Can you give latest Git a try ?

[Jayz2K]

Seems the problem comes from using the Prop in settings.xlm id="$INFO[Window(Home).Property(SetID)] " ...

Now I get what you mean. You also want to use a infolabel for the ID itself in the skinsettings.xml
I have just adjusted this. Can you give latest Git a try ?

Woohoo ! Works

I made a really quick test in situation but need to connect it to more complex scenarios to manage the whole Designer. That's not a light refactor but it's worth it. I will need some more time to fully report everything fine

Are props and/or infolabels also handled for <onselect> conditions and commands ?

Thank you very much for this awesome feature !

[User 224999]

amm, no errors now, but the "CustomPicturesBackgroundPath" is not affecting the backgrounds. even not the single rotating bg..
I also checked it on Titan, and also there the custom path is not working for me.

Can you check with latest Git ?
Also just found out that Titan has an error according to this, the name of the property is wrong so test with your own skin ;-)

[tomer953]

amm, no errors now, but the "CustomPicturesBackgroundPath" is not affecting the backgrounds. even not the single rotating bg..
I also checked it on Titan, and also there the custom path is not working for me.

Can you check with latest Git ?
Also just found out that Titan has an error according to this, the name of the property is wrong so test with your own skin ;-)

it still grabs from all the sources instead of my specific dir.

[User 224999]

Are props and/or infolabels also handled for <onselect> conditions and commands ?

Great that it's working, this will indeed save a lot of time and errors coding skin toggles/options.
Latest Git also has support to use infolabels on the <onselect> conditions and commands.

Just been testing this with Titan and it makes the skin code a lot more easy to follow.
Thanks for the idea.

[User 224999]

There seems to be a serious 2-3 second lag with latest versions of helper and emby plugin (at least). The lag affects all screens updates afai can tell.
This version 1.0.23 [ https://github.com/marcelveldt/script.sk...719e67799f ] works fine (in Titan & Eunique).
I havent tested past this version to determine where the lag was actually introduced..

The delay time seems to match the delay when info isn't cached, ie. on first entry to item.

Can you check this with latest Git version ?
Also, where does the lag occur ? Which properties ?

[User 224999]

it still grabs from all the sources instead of my specific dir.

Works fine on my testsetup. It even picks up the change without a restart of Kodi.
Sure you've set the correct skin string?

Skin.SetPath(SkinHelper.CustomPicturesBackgroundPath)

[tomer953]

damn, I forgot the "SkinHelper." prefix.
too many copy-paste in the recent days... sorry for bothering you...

thanks!

[Jayz2K]

Just been testing this with Titan and it makes the skin code a lot more easy to follow.
Thanks for the idea.

Indeed ! Much more readable and usable than looping onclicks IMO ... That was just an idea, thank you for bringing this to reality ! This is going to produce some great things

Edit : One last thing, I didn't really get the .label prefix stuff mentioned in the readme ?

[tomer953]

Marcel, could you consider to bump version plz?

[User 224999]

Edit : One last thing, I didn't really get the .label prefix stuff mentioned in the readme ?

The .label prefix will hold whatever label you've set to the value.
Example:

PHP Code:

<control type="button" id="23060">
    <label>[B]$LOCALIZE[31312]:[/B] $INFO[Skin.String(SubmenuLayout.label)]</label>
    <onclick>RunScript(script.skin.helper.service,action=setskinsetting,setting=SubmenuLayout,header=$LOCALIZE[31312])</onclick>
</control>