Progressbar issues (both WB 4.x and 5.x)

from Stardock Forums
Hi!

I have a small issue with the progress bars in WB, which happens in WB 5.0 and even in WB 4.x.
When the left a part of the progressbar gets covered, the progressbar behaves like its length was only the length of the visible area. So, when it displays a 50% value, it covers 50% of the visible area. It happens everytime when the left part of a skinned progressbar gets covered.

Troubleshooting info:
WindowBlinds 5 BETA Troubleshooting Report:

STATUS : WB+ SRV+ HLP+ UI+

WindowBlinds is installed correctly on this PC.

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(Fujitsu Siemens SCENICVIEW P20-2) 1 is attached to NVIDIA GeForce 6800 Ultra
'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.
'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.
3,256 views 2 replies
Reply #1 from WinCustomize Forums Top
Which version of the Windowblinds 5 Beta and which version of windows (including service packs) are you running?

Does this issue occur with any progress bar and consistently?

Does the progress bar have to be partially covered when it starts, or can a window be dragged over it during it's lifetime to reproduce this problem?

Thank you for reporting this issue.

-Mike
[Stardock Support]
Reply #2 from Stardock Forums Top
I have Windows XP SP2 (English) and WindowBlinds 5 4.90d[b].002.

This happens every time a progress bar gets partrially covered. Depending on how much it gets covered, it "adjusts" itself, when the next update occures.
It seems to occure constantly with any progress bar.

Take a look at this video:
http://web.t-online.hu/cobrati/ProgressBar.wmv
(The video was captured with Windows Media Encoder, using the Stealth OS skin. It seems like WME had some trouble capturing the transparent borders.)

Please note, that I also had this issue earlier WB versions, like 4.6, I was just too lazy to report it.
Star Control: Origins