[master branch on 1809] I think GlassOverrideAccent is broken (the inactive titlebar is always the same color no matter what)

[Luximoz]

So, I noticed I had my inactive titlebars looking awful where they would have the exact same color as active ones, I tried playing around with GlassOverrideAccent, ColorizationColorBalanceInactive, AccentColorInactive, and ColorizationColorInactive, and no matter what I do, I still get the same color on my inactive titlebars, I've tested this on both 1.2.1 and the new 1.3 version.

[ALTaleX531]

Because GlassOverrideAccent is used to replace a buggy effect called accent, it is not used to override your accent color.

The usual way to do this is to check the Title bars and window borders box in the Show accent color on the following surfaces section, then enable ForceAccentColorization. Next, you can change the AccentColorInactive to adjust the inactive title bar color.

[ALTaleX531]

They both use accent so there is basically no difference. Nonetheless, I don't recommend you to use OpenShell.

[DAPOPOBEFASTONYOAZZ]

This is old, but I had to comment.

I would similarly advise against OpenShell. It is not as robust as StartIsBack (which I know being paid software is a turn off...)

I would also advise against the uDWM.dll patch, you'll (likely) eventually screw something up and your install is corrupted to the point that even system restore won't save you.

AWM is a much safer alternative. Rather than overriding DWM, it injects its parameters into the DWM for you. It gives much better flexibility and is much safer to use.

Lastly, I recommend using WinPaletter to change your window colors, Both active and inactive. Changing your colors through the registry can be a little weird. Doesn't want to save your settings sometimes.

Edit: If you are wanting the standard difference between active and inactive colors, you should set these colors to the same in WinPaletter. If you're using GlassType 0 (Windows Vista style,) in your registry, you should change the first two hex values in your "AccentColorInactive" from FF to 80. This equals the same type of halving the opacity effect of window border colors that Windows Vista did for inactive window borders. When using GlassType 1 (Windows 7 style,) it is a little trickier. If the Color Balance registry key is lesser than the GlassOpacity registry key, you should leave the first two hex values of the "AccentColorInactive" key as FF. If the inverse is true (Color Balance key value is greater than GlassOpacity) then you should change the first two hex values of the "AccentColorInactive" key from FF to 80.

[Skyyblaze]

@DAPOPOBEFASTONYOAZZ Is there any chance that AWM will eventually work on Windows 11 24H2 now that we have OpenGlass and DWMBlurGlass working too?

[DAPOPOBEFASTONYOAZZ]

I wish I could say, you may want to direct that question to the developers of AWM. I have not tested AWM on Windows 11, but it sounds like you have and it doesn't.

But to expand on what I was saying for WinPaletter, I'd recommend setting your window colors, both active and inactive, to the same color, but changing your opacity in the registry value. Change the first two hexadecimal values from FF to 80, and you'll get an effect just like Windows Vista and Windows 7.

[Skyyblaze]

@DAPOPOBEFASTONYOAZZ I actually didn't try it since I assumed it wouldn't work anyway but maybe I should just test it and see what happens.