WB5.5: Program windows keep resizing

from Stardock Forums
I'm having a weird problem with WB 5.5 on XP SP2. I'm currently using 5.50.021 according to Stardock Central; System Information shows 5.5 build 92 x86.

In my email and news client (Turnpike), the message currently being read is shown in a separate window. What's happening is that each time a new window opens, it's bigger, in both dimensions. Then when it's practically full-screen, the next message opens in a tiny window, like a web pop-up. It's driving me crazy having to resize the window all the time

I've only noticed this in this one program, so far: ordinary My Computer and Explorer windows open to their normal size each time. Turnpike is an Explorer shell nameplace extension, so I can't simply exclude it from skinning. The problem only appeared after I upgraded and it happens with the majority of my skins. The only ones I've found so far that don't resize the window like this are Blackcomb, Aura and the XP and Windows Classic.

Yesterday I found a partial workaround; if I apply the XP default skin, then Aura, then my chosen skin, and close and re-open the program, that stops the resizing for that session, but on reboot the behaviour is back again.(I'm not sure if applying Aura after XP is necessary; will check that tomorrow.)

If anyone has any ideas on what could be causing this, I would be *really* grateful!

----------------
System info:

WindowBlinds version : WindowBlinds 5 (5.5 (build 92 x86))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

(HYUNDAI ImageQuest L72D Digital) 1 is attached to NVIDIA GeForce 6200

Wblind.dll 2007/02/21 15:06:20
Wbsrv.dll 2007/02/07 17:31:19
Wbconfig.exe 2007/02/15 13:35:52
Wbload.exe 2006/03/13 17:54:14
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/28 18:26:49
Wbload.dll 2005/01/22 18:05:07
windowblinds
2,587 views 5 replies
Reply #1 from WinCustomize Forums Top
Can Turnpike be added to the exclusion list to only use a specific skin? (like Blackcomb or Aura)
Reply #2 from Stardock Forums Top
Hi Bichur, thanks for the reply.

No, unfortunately I don't think it can, because it's an Explorer shell namespace extension -- if in Task Manager you right-click on the running Turnpike reader, and choose Process, you'll be directed to Explorer.

However, some development: yesterday I started having trouble with my computer not properly recovering from standby; twice the nVidia driver BSOD'd, except it wasn't a blue screen, just a completely blank black one. I reinstalled the driver and on opening Turnpike this morning was surprised to see the correct window size has stuck through the reinstall and reboot. so fingers crossed. . . I'll report back on how it goes.
Sins of a Solar Empire II
Reply #3 from Stardock Forums Top
fingers crossed


  
Reply #4 from WinCustomize Forums Top
I'm having the same problem with WindowBlinds 5.5 on Vista Business. It is mostly happening to Windows Live Messenger. Everytime I close the contact list, and conversation window, and re-open them, they get much bigger each time in both dimensions. It happens to other program windows as well. I am using the Optix theme, and below is my system information.
Reply #5 from Stardock Forums Top
Hi MasterSchwag

Sorry you're having this problem as well. I don't know if Vista has a default theme other than Aero, but in XP this is the workaround I've found:

Open the program, open WB config and apply XP default skin.
Open the problem window and size it how I want. Close window.
Re-open WB config and apply my chosen skin.

After this the window behaves properly and if I manually resize it, it stays that size., even if I close and re-open the program. However, when I reboot, the problem is back and I have to go through the above procedure again. (Note to Bichur: the crossed fingers didn't work, LOL)

I was interested to see you're using an ATI card. I was thinking of ditching the Nvidia and going back to my old ATI to see if it solved this, but since you're also having the problem it seems there's no point.