On my system had no need to change anything in the Precision and Diamond skins. From my experience these two skins are the only one that work perfectly as they are. I only would like to know in what control skinning part there is difference between let's say "Echo" skin and "Primo" skin by Essorant that I am not able to tweak "Primo" in the same way as "Echo". I mean, for "Echo" it's enough in SkinStudio to change "Normal Toolbars -> Button (6 State) -&
Lotzy
Here is the summary of fixes to do with SkinStudio: 1. For the skins included in the WindowBlinds install kit: a. Acrylic7 - not fixed, unable to open it in SkinStudio b. Change "Normal Toolbars -> Button (6 State) -> Text tab -> Text Colour" to OS Default for: Corporate Echo Eva Ice Lantana Modern The Captain Win8 Win8 Metro c. Ok as it is: Diamond Precision
Thanks @DaveBax. As I said in the OP, this settings "Normal Toolbars -> Button -> Text tab -> Text Colour" is changing the color of Classic Shell start menu items, but as @Nerius observed that setting will impact Windows 10 - System Menu bar as well.
@Nerius: Your are partially right ... "Colour 14" is just a color definition that can be associated to multiple controls. Indeed I did not notice that System Menu bar in Device Manager or Control Panel became invisible as the text color si white on white background. From what I was able to understand, "Normal Toolbars -> Button" element of the skin, configures the attributes of the elements you listed. But here is an interesting thing, the only skin that works well without the need to
As already was posted in this closed thread: https://forums.stardock.com/453109/page/1/ , there is a problem with WindowBlinds and Classic Shell start menu font color: start menu items font color appear dark in many WB skins, so with the usual Classic Shell start menu skins which are dark too, it's hard to read the menu items. From what I was able understand, it seem WindowBlinds controls the font color of Classic Shell start menu it