Obvious painting of skins

UI is not black :)

As a dab hand with the mouse I've always been very sensitive to the slightest delay in UI response, and thus have been a Windows Classic person, plus there wasn't any themes out there that really caught my eye. However, I wanted a more exciting desktop and WindowsBlinds not only promised that, but no loss of performance (or even a gain!) along with it. Because of that I purchased the product. However, I've found that the painting of windows is far more obvious when a skin is enbabled. This might be due to my choice of apps, I only work with a small number of windowed apps, but they are marked as theme aware which should make them fair game. For the follow examples I will use Mozilla Firefox and foobar2000.

With the Windows Classic skin (incidently, WindowsBlinds doesn't properly revert the title bar font) I can barely see the painting of the Firefox window as I restore and maximise it. The same is true when I load up foobar2000 behind it.

With the Simple Alpha skin I begin to see painting during restore and maximise which is further exaggerated once foobar2000 is behind Firefox (sticking out when the Firefox window is restored).

With a skin I found called Artwork the painting becomes even more obvious, but once foobar2000 is loaded behind Firefox we start to pass the point of tolerance where you're waiting a good half-second before the app has resized.

In the case of both Simple Alpha and Artwork, the border of an application draws over the top of the start menu?!

I tried enabling Hyperpaint and used both the minimum and maximum settings, but it doesn't seem to have helped.

My desktop is 1600x1200x32. My machine is as follows:

PIV 3Ghz
1GB RAM
System set pagefile
ATI Radeon 9800 Pro 128MB
128MB AGP Aperature
6,395 views 7 replies
Reply #1 Top
Sorry, this should be on the WindowsBlinds forums, don't know how it ended up here.
Reply #2 Top
I can't help you, but am curious about what a "dab hand" is...

(assuming something like quickness)
Reply #3 Top
What does the WB system information page in the configuration say?
Reply #4 Top
Dab hand = good with. Must be a UK thing

Hope this info helps! Sorry, I'd always ignored that link because I assumed it went to the Windows Systems Info tool.

WindowBlinds 5.0 System Information Report:

STATUS : WB+ SRV+ HLP+ UI+ TRAY+

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.

(Mitsubishi Diamond Plus 230SB) 1 is attached to RADEON 9800 PRO

Wblind.dll 2006/03/21 14:33:46
Wbsrv.dll 2006/02/05 13:58:22
Wbconfig.exe 2006/03/19 15:33:44
Wbload.exe 2006/03/13 18:54:12
Wbhelp.dll 2004/09/18 17:37:00
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2005/11/02 14:28:26
Reply #5 Top

I had exactly problem as you and I also have the same setup inc graphics card and browser.
When I installed WB5 it was running terribly, the computer took ages to start and when I opened a window I had to watch it become constructed before I could click in it  , my hand is also pretty dab, so with this sort of performance I dispaired, it only got better when I reinstalled windows.


Now, I think this is because for a week before hand I had been trying out lots of different shell replacement and desktop enhancement programs, including WB3 from a subscription to Object Desktop I had a few years back, so I reckon it was just clogged up to the max, now its running sweet

Reply #6 Top
dab hand....My 80 YO uncle uses that term a lot. I expect it means someone who's pretty good at something.


Posted via WinCustomize Browser/Stardock Central
Reply #7 Top
Did you by chance install the trial version before buying?

If yes, did you completely uninstall the trial version before installing the paid version of WB5? Not doing so will muck things up a bit - requires a complete uninstall, deletion of the WB directory & reinstall of WB5 (good to save a copy of the skins folders somewhere first). No sure why SD haven't put a detection & warning routine in the installer, but at least they tell you that in the release notes online.

If no, not sure what the problem might be, as it should run right quick on that rig.