Caption bar buttons mouseover problem

Hi.

After working on the caption bar of my copy of the Diamond theme, I find that the mouseover on the three buttons upper right works differently now: Originally, I can activate each button separately, now all three light up at once. The glows stay individual though.

Also, the Close button appears a bit "paler" now.

Where would I change these?

Thanks for helping,

Mubuk

10,339 views 4 replies
Reply #1 Top

Edit Titlebars and WindowFrames / Edit per pixel buttons, each button listed individually underneath.  I've never stumbled upon that particular anomaly though so I don't know what to tell you there.

There are actually 2 sections for 2 different kinds of frames and buttons, Per Pixel and UIS2.  The Per Pixel frames/buttons are what a person typically sees, used for windows such as Windows Explorer.  The UIS2 frames/buttons are used less often,  and a person probably needs to have identified a program that uses them before editing them, otherwise you're "skinning blind".  The only place I see them that I know of is my vintage Excel.

I'm hardly the Windowblinds/SkinStudio authority though, so of course anyone else is welcome to jump in.  :)  

Reply #2 Top

I second that motion. Stop the noise!

Could somebody please speak up who know what they're saying, please?

Reply #3 Top

Did you not understand my directions to the window button area?

Reply #4 Top

Yes, I did.

I was talking about the top right three buttons in standard window frames, nothing else. All I did was resize the two caption bar images in paint.net for Caption and Caption Glass, then resizing the "OS caption bar" value in "Extra settings" accordingly.

Still, when I load the original Diamond theme, every button in the top right of the caption frame reacts on its own at mouseover, whereas in my versions of it, all three light up if I touch only one of them. And they stay lit up until I mouseover the caption bar somewhere else.

EDIT: I redid everything in version 11 of SkinStudio, and now everything works as it should. So, I'm guessing, it was simply a bug in the software.

Thanks for helping,

Mubuk