Numeric args[]

[sub]

Does this mean that skins where skinners use periods will fail in those countries?

Yes, if you dont parse it that way. The skinhelper class parses all its floating point numbers this way.

[sub]

The skin is manipulating them

Code:

    <!-- placements -->
    <Placements>
        <Placement name="CoversItemNowPlayingArt" location="0,5" size="40,45"/>
        <Placement name="ListItemNowPlayingArt" location="36,45" size="40,40"/>
    </Placements>

Martin

I'd probably just have an <Element> defined for each, with the element having the 'location' and 'size' attributes defining their position, so that it happens automatically when you create the UiStatics for each, rather building your own logic to try and move/resize the one element. You could then conditionally choose which UiStatic gets added in GetRenderList(), depening on whether the list is in List/Cover mode. This approach would better match what I've done with all the other screens, and would avoid having to add these <Placements> tags, which was something I used in PVRX2, havent used anyway in NPVR's skins.

[whurlston]

I'd probably just have an <Element> defined for each, with the element having the 'location' and 'size' attributes defining their position, so that it happens automatically when you create the UiStatics for each, rather building your own logic to try and move/resize the one element. You could then conditionally choose which UiStatic gets added in GetRenderList(), depening on whether the list is in List/Cover mode. This approach would better match what I've done with all the other screens, and would avoid having to add these <Placements> tags, which was something I used in PVRX2, havent used anyway in NPVR's skins.

This is the scenario I had in mind with my UIStatic example. To be honest, I didn't remember anything about Placements.

[mvallevand]

I'd probably just have an <Element> defined for each, with the element having the 'location' and 'size' attributes defining their position, so that it happens automatically when you create the UiStatics for each, rather building your own logic to try and move/resize the one element. You could then conditionally choose which UiStatic gets added in GetRenderList(), depening on whether the list is in List/Cover mode. This approach would better match what I've done with all the other screens, and would avoid having to add these <Placements> tags, which was something I used in PVRX2, havent used anyway in NPVR's skins.

I guess because that would have been too easy. I've made the change and it is working just as well. It actually took a few more lines of code, but it should be easier to skin. Thanks for that. The Location info might come in handy

Sorry whurlston for not getting what you were saying before too.

Martin

[whurlston]

No problem. I was just wondering if I was doing it wrong.