Thank you Neil Banfield for fixing the Start Menu Issue youre the best!

I loaded up Stardock Central this evening at 5:59pm and found an update to the program Windowblinds 5. I installed it immediately and rebooted. Problem is fixed! Although wassup with the slightly slow start menu drawing on the skins affected by the previous start menu bug?

Otherwise im greatful
6,417 views 23 replies
Reply #1 Top
The speed of startmenu drawing should not have changed.
Reply #2 Top
I had updated my driver for my piddling video card - thought it was fine then got the blank start issue... updated WB yesterday, haven't had the blank issue yet.

thanks Neil.
Reply #3 Top
Hey Neil, I had not checked before so not sure if always has been but there is a noticeable draw difference for a per pixel and non per pixel start menu. Is that just the nature of per pixel.
With per pixel start I can see it draw from top left to bottom right.
My system, 2.4 gig celeron, 1GB ram, runs at 266 on celeron, ATI 9200SE 128MB video card.
Reply #4 Top
I'm still having a problem with the start menu. I open the start menu and when it closes broken images of it are still visible until I refresh the desktop. I just updated to the latest WindowBlinds and the issue still continues.
Reply #5 Top
I'm still having a problem


...so what else is new......  
Reply #6 Top
My problem is gone
Before version 5.01h(b).012, the Start menu had gaping holes when it opened & I had to launch it twice to use it. With the new build, the Start menu displays as expected on the first click each time. I've tried several wba's & so far, all is well.
Thanks!




Sorry WebGizmos, yrag's always right...
Reply #7 Top
...so what else is new......



Sorry WebGizmos, yrag's always right..




Reply #8 Top

WebGizmos: would the corrupt bits be behind per pixel things on the desktop?

If so, have you set your taskbar to semi transparent using an app?

Reply #9 Top
  @Yrag...he's always pickin on me!

No Neil...I don't use any apps other than WindowBlinds & ObjectDock. What happens is, I can open the startmenu which opens and displays fine...but then I can move my cursor to the desktop and click and instead of the startmenu going away parts of it are left behind until I rightclick & refresh. This doesn't happen will all skins though. But I just bought the Carbonix skinpack and its doing it with that skin now.
Reply #10 Top
Here's an example...
Reply #12 Top
Just tried that and no it doesn't...so its something to do with ObjectDock. Hopefully you guys can fix that.   
Reply #13 Top
OK...I just reloaded ObjectDock and tried again and it didn't do it. Go figure.
Reply #14 Top
OK..unloaded Carbonix (it wasn't doing it)...reloaded the skin I was using...Ecliz...with ObjectDock applied...then reloaded Carbonix and it did it again. So I have no idea at this point whats causing it.
Reply #15 Top
Hey Web.; how good a video card do you have. With my ATI 9200se it takes WB + OD + WindowFX(taskbar set to transparent) for start menu to corrupt when closing. Unload ObjectDock or turn trans. task, WindowFX off and all is well again.
Reply #16 Top
I have a Nvidia GeForce4 MX 440 with AGP8X and I never had the problem until lately. And it only does it with some skins..not all. Best I can tell it has something to do with ObjectDock. And I really don't want to have to unload things all the time to get other things to work since all I use is WB + ODPlus.  So hopefully they can fix it.   
Reply #17 Top
And its not like its a "major" problem...more of an annoyance than anything. Unless of course I sat here all day opening and closing my startmenu   
Reply #18 Top
If all else fails you could always



Reply #19 Top
  
Reply #20 Top
Are you using the latest version of Object Dock? Might make a difference
Reply #21 Top
No I don't have the latest one installed just yet...not sure if it should matter but ya never know I guess   
Reply #22 Top
...not sure if it should matter but ya never know I guess


but isn't it things like that they try to work out and fix with subsequent versions?
Reply #23 Top
But I never had the problem before so it was never an issue till now.