Mayhem3 skin

[MixMan]

It still has the same errors.

Martin

I can not reproduce the problems you are having with the GBPVR version you are using. I have no problems at all on a PC. Very strange....is it NMT related?

[mvallevand]

My problem is on the NMT but I believe the issue is your HD is 1920x1080 and you create image bigger than the 1280x720 screen

Code:

2009-08-03 09:01:44.691    VERBOSE    [6]     - adding render hash: static (CoverArt):1687,324,208,396:True

I can't use 1920x1080 either (first for performance of the OSD it is slower and overkill) but when I try it one of the objects is creating dimension not divisible by four which is a problem for the NMT.

Code:

2009-08-03 09:01:44.682    VERBOSE    [6]     - adding render hash: item pos info:887,669,116,36:False

Martin

[MixMan]

I think I know whats may cause your problem.
I was sloppy and just "moved" the Coverart image outside the screen.
I used the @previewimage instead. I will fix.

[MixMan]

Martin, try this video library skin file and ListView-Video.png


I ended up making a new skin with both SD and HD layouts.
The skin will be compatible with self extracting SFX skin pack that I had earlier Advisor/Basic skin for old GBPVR v0.9X skin. SkinPacks will be downloadable from my dev wiki.
But I guess it will take a couple of weeks before the new skin is ready.

[mvallevand]

MixMan that fixed the problems, and it is stable now on the NMT The metadata popup is probably not centred right,and I'd like to see a little more text, when I'm in list view, and finally I'd also like to see filename/folder.jpg replace the basic low lever icon, like the music plugin does, even when metadata isn't being displayed if that is possible. None of this is criticism, it is a nice move forward.

Now I am dieing to try with fanart.

Martin

[mvallevand]

MixMan I finally know enough about skins to figure out why the Mayhem3 was corrupting the NMT screen. The Menu skin.xml CurrentTime defaults cause too big a screen to be drawn.

Code:

        <CompositeImage name="CurrentTime" size="100,100">
            <DrawText text="@currentTime" loc="15,5" size="80,80" textStyle="CurrentTime" align="Center" />
                    <DrawImage filename="button_close.png" loc="85,0" size="3.7,5" valign="Top"/>
        </CompositeImage>

Cutting it down to this works for me much better

Code:

        <CompositeImage name="CurrentTime" size="90,30">
            <DrawText text="@currentTime" loc="15,5" size="80,80" textStyle="CurrentTime" align="Center" />
                    <DrawImage filename="button_close.png" loc="95,0" size="3.7,15" valign="Top"/>
        </CompositeImage>

Martin

[Fatman_do]

Not to butt in to this thread, but let me explain how pvrx2 skinning works in case there is any confusion on the the inns and outs of size and location.

<CompositeImage name="CurrentTime" size="100,100">

means draw this element at 100% "X" and 100% "Y". (regardless of screen resolution for pvrx2.exe compatible skins.)

<DrawText text="@currentTime" loc="15,5" size="80,80" ......

means draw this text at 15% over from top left of where this composite image starts, and 5% down from top left of where this composite image starts, with the size being 80% of "X" and 80% of "Y of this composite image, with this example being 100% of the screen in both directions.

What you did is limit the overall width and height to be just 90% "X" and 30% "Y" of the screen size. The resulting text, therefore, becomes a percentage of those values.

You could have also changed the loc="15,5" size="80,80" and achieved similar results.

Maybe this will help in understanding what the size and location numbers means to others as well for what is going on in the \skin2 folder. The values are "nested" to be a percentage of the parent element.

To add another level of confusion, any size and location listed in the "Placement" section of the skin, is the parent size/location of the CompositeImage.

[mvallevand]

Thanks Fatman_do it helps I think my preference is to keep the size of the elements less than 100,100 because this can stop a full screen write on the NMT.

Maybe you could explain how the offset value on the MVP/PCH works too, because this is what seems to cause problems.

Martin

[Fatman_do]

To be honest, I do not have a client device, so I had no reason to investigate this.

[MixMan]

I saw that in Mayhem3 size is 110% for...

<Placement name="CurrentTime" loc="10,2" alpha="150"/>

<CompositeImage name="CurrentTime" size="100,100">
<DrawText text="@currentTime" loc="15,5" size="80,80" textStyle="CurrentTime" align="Center" />
<DrawImage filename="button_close.png" loc="85,0" size="3.7,5" valign="Top"/>
</CompositeImage>

I will adjust and check other Themes so size is 100% in future.

But I'm planning to let Mayhem3 skin die, when the new skin is ready.
It will have Mayhem3 HD/WS as default theme, so it is the same but better.
I will have seltextracting ThemePacks as addons to change style of the skin.....as I had earlier for GBPVR 0.98 with the Basic skin.