Changing skin font or colour

[mvallevand]

Can a plugin direct NPVR to use a different named font or colour for an element than than the default defined by the skin? Using @is values to do this is cumbersome and I figure I must be missing something.

Martin

[sub]

No currently, but I can add something in the next build for you.

[mvallevand]

Perfect, something like

args["@Color"]="Test"; //just colour
args["@Font"]="DefaultReverseBlue"; //whole font

from the current skin or global.xml would meet most needs

Martin

[Jaggy]

As a skinner I'm not sure if I'm keen on this, what control are we going to have over these selections, particularly the font selection but even having the plugin deciding what colour to display would not be something I want?

[mvallevand]

Why Jaggy? I would not be calling the colour/font directly, I would be calling the colour/font that you set up on the skin.

Martin

[whurlston]

But each skin can have different named colors/fonts. Which would mean if you do this, you need to program specifically for every skin which could get more complicated than using @is values.

[Jaggy]

I did say.....

what control are we going to have over these selections

& after posting wondered if I was interpreting the request wrongly. I don't have a problem as long as we still have control of the fonts & colours within the skin, one of the most frustrating things about skinning is not having some control over how some items are displayed.

[Jaggy]

But each skin can have different named colors/fonts. Which would mean if you do this, you need to program specifically for every skin which could get more complicated than using @is values.

Unless it was done like sub had in the old TV Guide where there were special case fonts & colours for these items???????

[mvallevand]

I'm open to suggestions. What I am now doing is using the SchedulesDirect /WMC values in the unique_id field to colour code "EP", "SH", "SP" and "MV" records with

Code:

        <Text text="@Title" visible="@isSports" location="11,0" size="60,100" font="DefaultReverseR" align="Left" valign="Left"/>
        <Text text="@Title" visible="@isMovie" location="11,0" size="60,100" font="DefaultReverseY" align="Left" valign="Left"/>
        <Text text="@Title" visible="@isShow" location="11,0" size="60,100" font="DefaultReverseG" align="Left" valign="Left"/>
        <Text text="@Title" visible="@isEpi" location="11,0" size="60,100" font="DefaultReverse" align="Left" valign="Left"/>

To then add an @isItem or @isFolder makes it unmanageable, and that is with only four choices.

Martin

[Jaggy]

That looks like a good case to have available to use special case fonts & colours I mentioned above like the old TVGuide

Code:

    <NamedColors>            
        <NamedColor name="NormalListing" color="Vertical:#000044-#000077"/>
        <NamedColor name="ReminderListing" color="Horizontal:#000022-#000088"/>
        <NamedColor name="ScheduledListing" color="Horizontal:#220000-#880000"/>                                
        <NamedColor name="SelectedListing" color="Horizontal:#002200-#008800"/>        
        <NamedColor name="SelectedReminderListing" color="Horizontal:#000044-#0000BB"/>
        <NamedColor name="SelectedScheduledListing" color="Horizontal:#440000-#BB0000"/>
        <NamedColor name="ConflictListing" color="Horizontal:#442200-#AA5533"/>        
        <NamedColor name="SelectedConflictListing" color="Horizontal:#664422-#CC8844"/>
    <\NamedColors>