StartAllBack for Windows 11

[Wilda]

Hey guys! Is there any way to make StartAllBack taskbar darker to prevent burnin on OLED displays? It would be amazing to have such a feature embeded...

[SeaDog]

14 hours ago, Wilda said:

Hey guys! Is there any way to make StartAllBack taskbar darker to prevent burnin on OLED displays? It would be amazing to have such a feature embeded...

Try StartAllBack configuration > Advanced > Customize appearance. Choose a color to your liking or make it transparent.
Hope that helps!

[Tihiy]

20 hours ago, duk6046 said:

it's the same if shut down the hooking apps.

There's no 'hooking apps' in StartAllBack. You're using something else.

[snowlin]

Hello Tihiy

Windows 11 25H2 and later will support built-in dark mode.

However, the new dark mode conflicts with the dark mode in StartAllBack. Will this issue be resolved?

Thanks!

[Wilda]

6 hours ago, SeaDog said:

Try StartAllBack configuration > Advanced > Customize appearance. Choose a color to your liking or make it transparent.
Hope that helps!

That doesn't seem to do anything that would help with OLED screens, icons stay the same brightness/vividness...

[Tihiy]

1 hour ago, snowlin said:

However, the new dark mode conflicts with the dark mode in StartAllBack. Will this issue be resolved?

Yeah you can try test build https://startisback.com/StartAllBack_setup.exe

[SeaDog]

2 hours ago, Wilda said:

That doesn't seem to do anything that would help with OLED screens, icons stay the same brightness/vividness...

I saw an AutoHotkey script somewhere a couple of years ago. Let me check.
Here it is. It's a modified version of the original. Decide for yourself whether to use it or not.

Or make the taskbar dark and/or transparent *and* autohide it.

[snowlin]

6 hours ago, Tihiy said:

Yeah you can try test build https://startisback.com/StartAllBack_setup.exe

The effect is perfect!

[duk6046]

It occurs from a specific 24h2 build, old version SAB are same issues on current 24h2 build. there are no newly installed other apps. it seems conflict with a display environment.

Edited 10 minutes ago by duk6046