Community skin project

[Old Dog]

I started skinning about a year ago because the overscan on my TV clipped the Blue skin. Since then, Sub has added overscan compensation to "config.xml". Today I could swiich to Blue and adjust the overscan settings.

The Blue Skin layout still does not consider overscan. Should the standard skin we keep talking about consider overscan?

-Old Dog

[Old Dog]

The ability to swap and change the ListView.png ... would be a good adition too.

Please explain, what is "ListView.png", where is it used, and why do you want to change it?

[Fatman_do]

I started skinning about a year ago because the overscan on my TV clipped the Blue skin. Since then, Sub has added overscan compensation to "config.xml".

The Blue Skin layout still does not consider overscan. Should the standard skin we keep talking about consider overscan?

-Old Dog

I had forgotten about this. I remember it now, I think I still have your template laying around for it. I think it should then. I know HD sets and some graphics cards can eliminate this problem, but I don't know about MVP's.

Old Dog, what is a good number to look at for a no fly zone? 10-20 pixels per side?

[McBainUK]

The Blue Skin layout still does not consider overscan. Should the standard skin we keep talking about consider overscan?

Why create a brand new skin to solve too many problems. The issue that started this all off was the fact that so many skins are no longer useable because their xml files are out of date.

To solve this why not have a set of xmls (Chameleon) which are updated, idealy by the community. These xmls refer to images with set names. Chameleon has about 40odd images which cover 90% of the skin. Then for a subset of the images, the user can use AM to swap and change if skins are supplied as sets of images".

ps ListView.png is the backgroud to every list in the Chameleon skin. Currently its black but could be swapped out to suit the current look the user has (choice of buttons, background etc)

[Old Dog]

I had forgotten about this. I remember it now, I think I still have your template laying around for it. I think it should then. I know HD sets and some graphics cards can eliminate this problem, but I don't know about MVP's.

Old Dog, what is a good number to look at for a no fly zone? 10-20 pixels per side?

http://www.indiana.edu/~telecom/faculty/..._tips.html

BTW, check out my edited post.

[Old Dog]

Why create a brand new skin to solve too many problems. The issue that started this all off was the fact that so many skins are no longer useable because their xml files are out of date.

To solve this why not have a set of xmls (Chameleon) which are updated, idealy by the community. These xmls refer to images with set names. Chameleon has about 40odd images which cover 90% of the skin. Then for a subset of the images, the user can use AM to swap and change if skins are supplied as sets of images".

I'm sure you answered a question here, but not mine.

[Fatman_do]

ps ListView.png is the backgroud to every list in the Chameleon skin. Currently its black but could be swapped out to suit the current look the user has (choice of buttons, background etc)

Changing themes also changes these list backgrounds, but there is no mechanism to do so individually.

Chameleon does not take into account overscan. It might by accident, but I know I didn't take it into consideration since I skin on a laptop and my HTPC's video card is adjusted so there is no overscan.

Overscan needs to be supported I would think.

[McBainUK]

Not a reply but a comment on this:

Should the standard skin we keep talking about...

[Fatman_do]

http://www.indiana.edu/~telecom/faculty/..._tips.html

BTW, check out my edited post.

I didn't see anything with overscan, but there was usefull information there. I could have missed it.

After re-reading your edited post, I have to look at how this overscan correcting works in the config.xml file.

How does a skin work with this? Or am I not understanding something.

Are you referring to TV sets using rectangular pixels instead of square ones in general?

Signed, clueless in Michigan......

[Old Dog]

Fatman_do,

I thought the link I posted answered you overscan question but now I see that it doesn't. You should allow 5% per edge for overscan.