[BUG] Skinned themes fail to load window title bar skin if window is sized to fill the whole desktop area

from Stardock Forums
Using current updated version of Object Desktop Ultimate apps (as of 24 June 2008), XP Pro SP2 or SP3, along with at least one them (the "LK" theme from DuoPixart), the title bar skins of several apps as well as Windows XP Explorer windows, will fail to load if window is sized to fill the entire desktop area (but not actually "Maximized").

Details:
1 Close or minimize all running application windows
2 Open an application such as Thunderbird, Firefox, or a Microsoft Explorer (not Internet Explorer) window browsing one of your drives/folders.
3 Right-click on the XP task bar and select either Tile Windows Horizontally or Tile Windows Vertically such that the app you've opened fills the entire desktop.  Do not "Maximize" the window.
4 Observe whether or not the app/explorer window is missing the title bar skin, or if the title bar appears to be missing entirely.

Temporary work-arounds include doing one of:
* Maximize the the window, then restore the window to it's original size.  The skin/title bar will now appear.
* Don't fill the entire desktop with the app window, just resize the window so that it is smaller than the desktop resolution, then close and re-launch the app/window at it's new, now smaller, size.
* Launch Windows Blinds or Theme Manager and re-apply the theme or make a change to a theme setting, undo that change then click Apply.


I'm not 100% certain that the issue is specific to just certain themes, as I've not tested out all of the themes I've installed, nor have I tested all applications and their windows.  However, at the moment, I'm leaning towards this being a Stardock app issue, and not necessarily an authored theme issue.

[Please advise if more info about my system is required.  There are a lot of variables, I know, but it would be great to nail this down to either the skin theme or one or more of the Object Desktop apps.]


10,523 views 12 replies
Reply #1 from WinCustomize Forums Top
WB system info?


I sized FF to have about an inch or so all around

running Vienna2

right clicked bar and chose one of the 'tile' options
all seemed well
then I clicked FF to open a new window
on the 2nd window - absolutely no title bar showing

tried it with:

LK
TTD
Natural WB
Grave Paradise

same result

would have tried others but it was hell getting the window to function properly after each test

WindowBlinds version : WindowBlinds 6.1 (build 55 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.

(hp pavilion f50) 1 is attached to NVIDIA GeForce4 MX 440 with AGP8X

Wblind.dll 2008/05/06 15:25:20
Wbsrv.dll 2008/04/28 11:35:10
Wbconfig.exe 2008/04/29 21:02:32
Wbload.exe 2008/04/28 11:35:14
Wbhelp.dll 2008/04/28 11:35:07
Wbui.dll 2008/04/28 11:35:05
Tray.dll 2008/04/28 11:35:21
Screen.exe 2008/04/28 11:35:18

nView is off, using Driver Version 6.14.10.9371



Reply #2 from Stardock Forums Top
Just to make sure the question gets asked. Drivers up to date Aesir? I will be testing this out in the morning of course but I wanted to do the follow up.
Star Control: Origins
Reply #3 from Stardock Forums Top
WindowBlinds version : WindowBlinds 6.11 (build 58 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.

(SyncMaster 226BW,SyncMaster Magic CX226BW(Digital)) 1 is attached to NVIDIA GeForce 7950 GT

Wblind.dll 2008/06/20 21:14:20
Wbsrv.dll 2008/06/13 11:24:10
Wbconfig.exe 2008/06/20 21:14:32
Wbload.exe 2008/02/14 11:05:14
Wbhelp.dll 2007/07/24 10:21:07
Wbui.dll 2007/11/06 11:13:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2008/06/13 11:24:09


NVIDIA System Information report created on: 06/26/2008 05:34:55
System name: WOPR

[Display]
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2009 MHz)
Operating System: Microsoft Windows XP (Service Pack 3)
DirectX version: 9.0c
GPU processor: GeForce 7950 GT
ForceWare version: 175.16
Memory: 512 MB
Video BIOS version: 5.71.22.42.77
IRQ: 17
Bus: PCI Express x16

[Components]

nvCplUIR.dll 1.4.13.09 NVIDIA Control Panel
nvCpl.cpl 1.5.2400.10 NVIDIA Control Panel Applet
nvExpBar.dll 1.5.2400.10 NVIDIA Control Panel
nvCplUI.exe 1.5.2400.10 NVIDIA Control Panel
nvWSSR.dll 6.14.11.6218 NVIDIA Workstation Server
nvWSS.dll 6.14.11.7516 NVIDIA Workstation Server
nvViTvS.dll 6.14.11.7516 NVIDIA Video and TV Server
nvMoblS.dll 6.14.11.7516 NVIDIA Mobile Server
NVMCTRAY.DLL 6.14.11.7516 NVIDIA Media Center Library
NVOGLNT.DLL 6.14.11.7516 NVIDIA Compatible OpenGL ICD
nvDispS.dll 6.14.11.7516 NVIDIA Display Server
NVCPL.DLL 6.14.11.7516 NVIDIA Compatible Windows 2000 Display driver, Version 175.16
NV4_MINI.SYS 6.14.11.7516 NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.16
NV4_DISP.DLL 6.14.11.7516 NVIDIA Compatible Windows 2000 Display driver, Version 175.16
nvGameS.dll 6.14.11.7516 NVIDIA 3D Settings Server


The issue pre-dates the currently installed nVidia 175.16 driver package. Took me a while to get around to posting about the issue - once I started seeing a reproduceable pattern. Also, I'm reasonably certain the issue pre-dates this current version of WB installed on my system.

Other drivers and OS are updated regularly as well. I can provide more info - just let me know what type of data is desired (and the preferred system info applet/utility to use).

Reply #4 from Stardock Forums Top
Just to make sure the question gets asked. Drivers up to date Aesir? I will be testing this out in the morning of course but I wanted to do the follow up.



Wanted to know if you (SeaBass, or anyone from StarDock) were able to repro the issue described. If not, is there any more info I can provide that will help to track this down?

As a side-note, nVidia updated their driver set from 175.16 to 175.19 since I'd first posted of the issue. I updated accordingly, and there's no change to the described behaviour.
Reply #5 from Stardock Forums Top
I was testing this and noticed that you are still on the beta. If you turn off show pre-release and update does the same problem still occur?
Reply #6 from WinCustomize Forums Top
I was testing this and noticed that you are still on the beta. If you turn off show pre-release and update does the same problem still occur?


6.10.084 - 07/15/2008

WindowBlinds version : WindowBlinds 6.1 (build 55 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.

(hp pavilion f50) 1 is attached to NVIDIA GeForce4 MX 440 with AGP8X

Wblind.dll 2008/05/06 15:25:20
Wbsrv.dll 2008/07/10 15:02:10
Wbconfig.exe 2008/04/29 21:02:32
Wbload.exe 2008/04/28 11:35:14
Wbhelp.dll 2008/04/28 11:35:07
Wbui.dll 2008/04/28 11:35:05
Tray.dll 2008/04/28 11:35:21
Screen.exe 2008/04/28 11:35:18


yes
Reply #7 from Stardock Forums Top
I was testing this and noticed that you are still on the beta. If you turn off show pre-release and update does the same problem still occur?




Bichur, if your 'yes' response indicates that you're not running a beta version of WB, then thanks! Because you'd saved me the trouble.

SeaBass if you've not been able to repro the issue, please let me know if there's additional info I can provide (e.g., DXDIAG output)?





Reply #8 from Stardock Forums Top
I was testing this and noticed that you are still on the beta. If you turn off show pre-release and update does the same problem still occur?


This is probably a user issue... but I've not been able to downgrade.

In Impulse, I right-click the Stardock icon, and select Preferences.
Under General, I deselect Show Pre-Release (Alpha/Beta) versions and click OK to accept the change.
I right-click the Stardock icon and choose Check for application updates.

No 'updates' are found.

Short of uninstalling/re-installing (which I'm hesitant to do) is there a reliable method of downgrading from alpha/beta versions to the most recent release version of WB?

[Updated]
After posting, I downloaded/installed the current beta (as of the time of this posting). That introduced a new set of issues, including a WB prompt indicating that I needed to disable anti-spyware/virus software and/or run an additional process if after rebooting that notice still appeared. It did, and my taskbar was no longer skinned. Fiddled a bit with trying to get it to apply the skin, then just uninstalled WB, re-installed the non-beta release version. This eliminated the 'new' issue introduced with the current beta version, but testing demonstrated that the issue outlined in this topic remains.

So, SeaBass, to answer your short question with a long answer, "Yes, the problem I described with titlebar skins not being applied correctly when a window is sized to take up the entire desktop area does exist in the release version on my system."

Reply #9 from Stardock Forums Top
Well, yes, I'm a nag, but I notice the same issue reported originally with the "MyColors" Burgundy theme I'm currently enjoying. Titlebars are invisible if an app window opens at launch to fill the desktop (but not "Maximized")

Please advise if Stardock support requires additional info not already provided in the topic and/or if the issue has been successfully replicated in testing (at which point I'll let the topic die and wait patiently for a patch/fix). Thanks!
Reply #10 from WinCustomize Forums Top
Reply #12 from Stardock Forums Top
Thanks for the response.