INTERACT FORUM

More => Old Versions => Media Center 11 (Development Ended) => Topic started by: lalittle on November 06, 2003, 12:38:52 am

Title: PixOS skin -- what happened?
Post by: lalittle on November 06, 2003, 12:38:52 am
I just upgraded to the new build (296) and the PixOS skin is messed up.  It's suddenely a greenish tint (rather than the normal neutral blue) and the "Show Grid Lines" option no longer has any effect -- i.e. you don't get the alternating shaded lines in the lists.  This current screen has an overall "too bright" look with EXTREMELY light tints to all the colors on the bars.  The previous PixOS was much, MUCH more pleasing to the eye than this one.

I installed it on a second system and got the same results, so this isn't a problem with the actual system.

Were these changes intentional (I just can't believe they could be)?

Thanks,

Larry
Title: Re:PixOS skin -- what happened?
Post by: jcouch93 on November 06, 2003, 12:48:20 am
Quote
9. NEW: Added "Skin Effects" dialog which allows customization of MEGA-ME coloring and appearance

That's what happened.  Go into the Skin Effects part of the options and play around...

phatrabt
Title: Re:PixOS skin -- what happened?
Post by: gpvillamil on November 06, 2003, 02:21:28 am
Go to Tools/Skins/Skin Effects and select "None" from the drop-down menu in the dialog. That will everything back to normal.

However, you might want to play around - maybe you'll find something pleasing!
Title: Re:PixOS skin -- what happened?
Post by: nameless on November 06, 2003, 03:56:51 am
They made "Add color (high contrast)" the default just to see how many feathers they could ruffle!  It threw me for a loop for a minute, that's for sure.
Title: Re:PixOS skin -- what happened?
Post by: lalittle on November 06, 2003, 04:02:38 am
Thanks for the fast responses -- that took care of it.  I wish all help forums were as responsive and helpful as this one.

Larry
Title: Re:PixOS skin -- what happened?
Post by: Matt on November 06, 2003, 08:43:52 am
It was a bug that it's on by default.

Next build will fix it.