WindowBlinds 5.1 inconsistent behaviour in 'per application' setting

from Stardock Forums
I am using the latest version of WindowBlinds 5.1 under Windows XP SP#2 and have found that depending on where you set the skin to use, the results are different.

For example, if I set the system wide skin to any USI1 or USI2 skin, then my music manager program (Helium) refuses to load. Ok, if I create a 'per application' setting for Helium and tell WindowBlinds to exclude helium2006.exe from all skinning which is what the helpfile suggests, then Helium loads without a problem as you'd expect.

However, if I then change that 'per application' setting to use a specific skin for Helium (and it doesn't matter what skin I choose, USI1 or USI2 compatible, or even exactly the same skin as the system wide skin), then Helium works fine.

This doesn't seem consistent, it's like an application interacts with a system wide skin and a per application skin differently, even if it's exactly the same skin???

Is this correct and if so, why does it happen?

Many thanks...
windowblinds
2,987 views 5 replies
Reply #1 from Stardock Forums Top
Sorry, I forgot to add the WB System Info which is as follows:

WindowBlinds 5.1 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.

(ViewSonic VP930 Series) 1 is attached to NVIDIA GeForce 6600 GT

Wblind.dll 2006/10/09 11:24:20
Wblind64.dll 2006/10/09 12:51:37
Wbsrv.dll 2006/10/09 11:40:18
Wbconfig.exe 2006/10/10 17:39:13
Wbload.exe 2005/12/21 01:04:47
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/28 19:27:49
Reply #2 from WinCustomize Forums Top

A per app skin and a systemwide skin will appear almost the same to the app.  The only difference is a systemwide skin can set systemwide colours & fonts.

Some apps are unable to handle certain font combinations set by a few skins.

I tried that app here and it seems to load perfectly without any issues here.

Galactic Civilizations IV
Reply #3 from WinCustomize Forums Top
This

WindowBlinds appears to be activated on this PC


says paid


This

Wbload.exe 2005/12/21 01:04:47
Tray.dll 2006/04/28 19:27:49


says trial


you might try uninstalling, rebooting, then reinstalling via SDC

Reply #4 from Stardock Forums Top
That did the trick! I have rebuilt my PC and restalled WindowsBlinds 5.1 and the problem has gone away.

One thing I have noted is that the version info is still the same as before, ie...

WindowBlinds 5.1 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.

(ViewSonic VP930 Series) 1 is attached to NVIDIA GeForce 6600 GT

Wblind.dll 2006/10/09 11:24:20
Wblind64.dll 2006/10/09 12:51:37
Wbsrv.dll 2006/10/09 11:40:18
Wbconfig.exe 2006/10/10 17:39:13
Wbload.exe 2005/12/21 01:04:47
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/28 19:27:49

.... This is installed straight from the download link I got with my order and activated as per the instructions in the email, so there shouldn't be anything 'trial' about it???
Reply #5 from WinCustomize Forums Top
Maybe not - I don't work for stardock, i've just been using WB 3yrs and can access (via SDC) the history files.

the 5.1 release should be:

Wblind.dll 2006/10/09 10:24:20
Wblind64.dll 2006/10/09 11:51:37
Wbsrv.dll 2006/10/09 10:40:18
Wbconfig.exe 2006/10/10 16:39:13
Wbload.exe 2006/03/13 17:54:14
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 21:29:06
Tray.dll 2006/04/13 17:29:23

hours fluctuate based on your location and the server's - but the dates don't


From personal experience, I think you're better off uninstalling, rebooting, getting Stardock Central, register in SDC, then use it to download/install - SDC will also alert you to any updates you may be entitled to.

or just try updating via SDC after entering your serial - register is under tools

Stardock Central