StartIsBack's AfterglowBalance is influenced by its opacity slider #315
Unanswered
TheInsane101
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I noticed that the value of Startisback's opacity slider for the taskbar and start menu changes its AfterglowBalance layer from DWMBlurGlass, but that only applies to the blur of the TB & SM and not the rest of the UI, making the blur inconsistent.
When you disable the "use custom taskbar/start menu colour" option so that SIB uses the system accent colour, its opacity value is fixed at 77%. Therefore, when "Override Accent colour" is enabled in DWMBG, the SIB elements have a higher AfterglowBalance than the rest of the UI.
For example, here I have a theme where DWMBG's afterglow value is 0.15, and SIB is set to use the system accent colour, so its opacity is locked at 77%.
Here is what a window and the TB look like with "custom TB/SM colour" option disabled:
Notice that the taskbar and start menu are significantly brighter than the window due to the higher afterglow.
When you enable the custom colour option and set the SM & TB's opacity sliders to the same value as the AfterglowBalance value of DWMBG (in this case, set SIB's opacity to 15%):
The start menu and taskbar now have the same afterglow as the window, so they're as dim as the window.
When you disable the custom colour option (so it's back to 77% opacity) and instead match DWMBG's afterglowbalance with SIB's opacity (so in this case, afterglowbalance is set to 0.77):
Now the window has the same raised afterglow that the start menu and taskbar had at the beginning of this experiment.
The only workaround for this at the moment is to enable the "set custom colour" option and manually adjust SIB's colours and opacity every time you change the afterglowbalance value in DWMBG and the system accent colour, which breaks the immersion of the SM & TB being able to change their colour to the system colour without any issues. Can a workaround be found to prevent SIB from changing any of the ColorizationBalance values, or will we need a modified or updated version of Startisback?
Beta Was this translation helpful? Give feedback.
All reactions