Here's my software setup:
- Win 8.1 Pro
- WSB v1.5.6.3 Beta
- UxStyle
NOTE: I switch off between using OldNewExplorer depending on what I'm experimenting with. In this example it's not enabled.
I finally got around to experimenting with the original question from the original post:
I've noticed that even in aero.msstyles there seems to be some conflicting properties between what is inherited vs what is set on the following paths for NavBar stuff:
Toolbars, Headers, & Rebar > Rebar > NavBar > Basic > Max > Inactive > Background
Toolbars, Headers, & Rebar > Rebar > NavBar > Basic > Max > Active > Background
Here's a snapshot from the listed properties in WSB:
Given the apparent redundancy I tried clearing those duplicate un-inherited properties out. The result was unstable and ugly:
As you can see the NavBar is colored properly (mostly), but now the rest of the Personalization window is all futzed up.
I tried following Panda's method for properly theming the NavBar and got the same result, but I'll be honest I probably missed something. I'm going to try again, but I wanted to double-check on this apparent conflict/duplication of properties. Is it me, or does that not look right?
On a related topic, is it possible to use any combination of properties in an msstyles file? Such as using BGFILL types instead of images or vice versa in any given element? Or is it not quite that modular?
EDIT: I got Panda's bit to work! It seems the more I tinker with someone else's theme, as opposed to the default Aero, the more problems I get. I guess I should stick with modifying a copy of default aero until I find my way around WSB better...