Windowblinds painting issues.

I have noticed, as I am sure most have, that Windowblinds fails to paint the GUI in allot of cases. I was hoping a new version would fix it but, it hasn't. Things like, window frames not painting when a non maximized window is scaled to full screen size. On occassion after a boot or reboot there is no skin applied whatsoever. I haven't worked o a skin in awhile, I'm almost afraid to see all the SkinStudio bugs still present. It's for these reasons I haven't made a skin in a while. Just sick of fighting with bugs. I don't know how many times I have been forced to reboot because these buggy apps failed to function properly. Don't see me buying anymore software for a loooong time. Corporate greed is a shame. And on top of that, these new servers suck. Most of the time the website isn't even accessable. The other times it's slower than hell or just refuses to open other pages once you get to the main. And I PAID to be on it. Great job. This website sucks.

But hey, Galactic Civ is out though...
19,071 views 32 replies
Reply #1 Top

I am not aware of any problems with WB not painting the GUI.  Could you provide more information such as the skin in use and screenshots of the problems please.

Regarding the new servers, I am not sure if the site has been moved over to them yet.

Reply #2 Top
I'll put together a package. You got an email I should send them to?
Reply #3 Top
Maybe it's because I'm computer illiterate and don't tweak, but I haven't had the non painting or no skin issues.
Reply #4 Top

So far WB5.01 is functioning fine here on XP Pro /SP2 and many prominent company apps from 2002 through 2005:

Office XP

Photoshop 7, Illustrator 10, CorelDRAW 12, Painter IX.5 (with the exception of resizing in conjunction with skins made for WB4.6), Acrobat 7, Bryce 5, Poser 5, etc.

The one exception seems to be ImageReady 7, which is not skinning the titlebar. I have not yet tested this with anything other than StealthOS (compact) - the alpha version.

Neil, I will create a post with some screenshots sometime this week illustrating the Painter IX.5 resize issue, and the ImageReady titlebar issue.

Reply #5 Top
I will take screenies. I have seen since the update...

1.Windowframes not painting and using the generic windows skin.
2.Start menu displaying trasperancy when there was none, or it was open windows displaying OVER the start menu(not sure which)
3.Shutdown dialog displaying the transparent parts of an image which should be invisible.

These are random events but I will try to "make" it happen and get screenshots. Mostly noticed after a reboot.
Reply #6 Top
Normally I would think that contacting support@stardock.com would be the way to resolve issues with Stardock products. There's no problem posting request for help in the forums either but without the irrelevant extras such as "Corporate greed is a shame. And on top of that, these new servers suck."

Most users here are more than happy to assist in trying to help out other users.
Reply #7 Top
Have you tried starting half a dozen threads in the forums? That sometimes works.
Reply #8 Top
I have run into problems between using Skinstudio and Windowblinds. Skinstudio (since the latest update) crashes/closes quite often. It will randomly paint things classic. Rebooting or reapplying a few times helps but not always solves the problem. What always fixes the classic problem is...unload windowblinds, open Skinstudio, reapply whatever skin I choose and all works fine. Reapplying using Windowblinds doesn't usually work. Only using Skinstudio to apply fixes it. I hope that makes sense to someone. I haven't had time to investigate (uninstall/reinstall) yet but I saw the post and perhaps part of the problem is using Skinstudio with Windowblinds at the same time. People may not run into the problems unless they are using Skinstudio. When I have the time, I will try to be clearer about the problems. It just seems since the latest updates, I am spending alot of time getting the GUI back to the way it should be when it goes classic. Not complaining, just noting that I have run into similiar problems.
Reply #9 Top
I have sometimes found that when loading or unloading a skin, WindowsBlinds will not always be entirely successful, leaving you with a half and half taskbar or something. Also the start menu is overdrawn by the borders of any open window.
Reply #10 Top
Have you tried starting half a dozen threads in the forums? That sometimes works.


Have you ever tried using a website that doesn't respond correctly?
Reply #11 Top
Thanks Craig, at least one person here has used this software and has somewhat of a clue as to what I am talking about. As an example, I just got back on my PC from a cold boot. When I get to desktop, WB isn't loaded at all. I have a plain classic. I have to reload WB to see the current skin. This has been happening since before the update. Sometimes WB just doesn't load. Taking a screenshot of it won't help, it will just look like I unloaded WB.

As far as the multiple posts are concerned, when creating this post, this website decided to freak out, like it always does, and refuse to advance to the next page. SO DON"T BLAME ME!!! I am not the one that just got nice shiny new servers. You would think having a subscription to this site would get you something other than...

....a subscription to this site. But, as a WC subscriber, I am forced to wait behind the millions of non-subscribers that are taking up my bandwidth. SUBSCRIBERS SHOULD TAKE PRECIDENT OVER NON-SUBSCRIBERS. It's a cold slap in the face to support a company with your money, only to get the same treament as those that don't. My 2cents.

EDIT: If Stardock needs someone to set their servers up properly, I can always drive over and take a look. I am right next door and can do the job ten times over.
Reply #12 Top
As a side thought, if Stardock needs some "help" with all the stuff they have going on, and in their words they are spreading it thin, I live a state away and will glady relocate if given a job. I have too much free time as it is. I have ample qualifications and have been a PC junkie since about '92. So experience isn't an issue. Either are certifications.

Stardock...hiring???
Reply #13 Top
Could you possibly post the System Information from the WindowBlinds Configuration screen. At least that will give a starting point to work from.

Not sure if you are looking to solve your issues with the programs or find employment with Stardock. If the latter, I don't believe they look in the forums for suitable candidates. Perhaps sticking with the troubleshooting issue would be best.
Reply #14 Top
Stardock...hiring???


https://www.wincustomize.com/Forums.aspx?ForumID=153&AID=107503#831611

5th paragraph

Reply #15 Top
I have sometimes found that when loading or unloading a skin, WindowsBlinds will not always be entirely successful, leaving you with a half and half taskbar or something.


This happens a lot when I change skins or when I reload a skin after making some edits with SKS. Certain graphic elements will be corrupted or unskinned & reloading the skin fixes things. Main reason I'd really like to have that "Reload current skin" option back in the WB SysTray icon context menu. Seems silly to have removed it, but that's just me.
Reply #16 Top
Stardock...hiring???


Link

5th paragraph


TX, I'll check into that.
Reply #17 Top
This is one example of a WB painting issue. Note the taskbar, the black areas should be transparent, displaying the wallpaper. This is one that's less critical IMO, as I only see this particular issue after exiting a game. More than likely just having a problem taking back the GUI from the game (no game in particular, does it with a few). The only solution I have found is to reload the skin.

I have found a few others, will post screenshots when I get them.

Reply #18 Top
Still waiting for the System Information from WindowBlinds Configuration. If you can post that here it would help.
Reply #19 Top
If you can post that here it would help.


How would that help? Who are you anyway?

Reply #20 Top

It lets us see if all the files are correct etc.

Regarding that wallpaper issue, you should find resizing the taskbar would fix the problem as well.

Reply #21 Top
It lets us see if all the files are correct etc.


I get ya, I meant no disrespect.

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.

( SyncMaster 190N(M)/192N(M)/193N(M) ) 1 is attached to RADEON 9800 XT - Secondary

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

Regarding that wallpaper issue, you should find resizing the taskbar would fix the problem as well.


That's easier than reloading. TX.



Reply #22 Top
Just changing the taskbar from locked to unlocked works too
Reply #23 Top
Just changing the taskbar from locked to unlocked works too


This happens when using SKS and applying a skin in progress on my system. Locking and unlocking fixes. This happened when using the ATI 9800 se, and I now have an nVidia 6200 that has no problems with the transparency/transluscency effects generated by WB or WinFX.

Before upgrading my graphics card, I also had the same issue Night Train describes above. This was compounded by the fact that I was overclocking from 1.8 to 2.3 ghz on my CPU.At the full 2.3 g's, when saving and applying a skin in the works, SKS would freeze and "not respond" for as long as 10 minutes and then suddenly apply the skin.

In my opinion, most of the issues described in this thread in regards to WB painting/rendering is in the graphics card or drivers thereof.

Good luck, and happy skinning.
Reply #24 Top
Scorpio: that may well be...

Too bad I don't have a second PC handy.

Also, I haven't tried messing with SKS since the update.
Reply #25 Top
Well Hankers, ya gonna fix this now that you have my sacred system info?


I didn't think so.