Buggy taskbar buttons & badly scaled tray expander icon

Windows 10 w/ some DPI scaling

Links: Picture of Issues, Windows Version, Windows Blinds Version

I have DPI scaling of 150% on primary monitor, and 100% on secondary. The pictured task bar is on the secondary monitor, and I typically only have the taskbar on the secondary.

First issue - seemingly randomly, part of individual taskbar button rendering will move several pixels in. Example on the Opera icon at the left of the screenshot. This can occur to both the focused and non-focused buttons. This may occur, but is not consistently reproducible when switching focused windows. This can be fixed by mousing over the broken button(s) or clicking on the taskbar, however it will return. Typically, one or more buttons will be in this state within a few minutes of normal usage without mousing over the taskbar. 

This issue is present on the primary monitor when the taskbar is enabled for that screen.

Second issue - the tray expander icon is rendered at 150% on the 100% scaling screen. It renders at 150% scale on the 150% scale screen.

Both issues are present across all of my installed themes.

Yes, I restarted after installing.

20,214 views 16 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. First any reason you're not updating your Windows 10 to latest release version? V22H2? V20H2 was released 3 years ago. A lot have change on Windows taskbar since than. When WB11 released a lot has been done on it to cope with latest Windows taskbar. Would like to recommend you to update your Windows 10 to V22H2. That we can see if the issue still there and work the issue from there.

Thanks
Basj,
Stardock Community Assistant.

Reply #3 Top

Please post screenshot of your issue using default skin that come along with Windowblinds. Try Diamond or Corporate.

Thank you,

Basj,
Stardock Community Assistant

Reply #4 Top

In order to keep my list clean and useable when switching between preferred styles, all default skins have been uninstalled, and there appears to be no way to re-add them.

Reply #5 Top

You can uninstalled and reinstall Windowblinds. It should add those default style.

Thank you,

Basj,
Stardock Community Assistant

Reply #6 Top

I think they recently started including the wba's for installed skins in a subdirectory of the skins, at least I'm seeing it.  Look in Public Documents/Stardock/Windowblinds/IncludedWBAs.

+1 Loading…
Reply #7 Top

Large tray expander icon on Diamond.

Large tray expander icon on Corporate.

Button rendering issues are not present on either official skin.

Fiddling has shown that the intermittent button rendering issues are specifically present on themes where the margins for the button are larger than the width of the button. Skin creator has been messaged, but the fact that it's an intermittent issue means there's probably something that can be done to fix it on the app end.

Reply #8 Top

Please post some of the skin that showing the issue so we can verify it. Preferably those non master/pay skin please, with link to download will be great.

Thank you,

Basj,
Stardock Community Assistant

Reply #10 Top

I tested and it look like the issue on taskbar buttons is on skin setting. When using combine taskbar button with hide text. The left and right margin that set too big will overlaps each other and causing the issue. Changing that value resolve the issue. Refer screenshot below

Turning the left and right margin down to 10 on both, from what I can see should not change how the author wanted the taskbar to look.

Thank you,

Basj,
Stardock Community Assistant

Reply #11 Top

I have already made those edits on my end.

Any ideas on the tray expander icon?

Reply #12 Top

For, Tray expander icon, I do not see the issue. Below is screenshot on my screen with 150% scale applied.

Thank you,

Basj,
Stardock Community Assistant

Reply #13 Top

I suspect it may be specifically caused by my main taskbar being on my secondary monitor, and the primary monitor being at 150% scale. Also, this may only be noticeable after a reboot.

Reply #14 Top

Okay, after testing it I can reproduce your issue. I think this is what you're looking at too.

I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #15 Top

Hello,

Sorry to hear you are having trouble.

I have placed an internal ticket to have it reviewed.

Internal ref: ODNT-7464

Thank you for the feedback.

Sean Drohan
Stardock Product Lifecycle Manager