I dropped the slider down one notch from full and indeed the window frame right paints correctly now. So, a BIG thanks for recognizing that.

However, it didn't affect the painting issues I'm having with menus & MDI buttons - they still paint the same. With due respect, those painted flawlessly on this rig with 5.49 (even with full hardware accel) so it's hard for me to accept it is only the ATI drivers - something about the way WB paints menus must have changed with 5.50 & up. I would love to update these drivers but they are a proprietary Fujitsu set that I can't update, even using Patje's Mod Tool. Being a notebook with integrated graphics (and my primary business rig), I'm a little leery of how forcing a change might negatively affect the system, anyway.

I'm using .tga images for the menus with only 4 trans pixels, one in each corner, in case that somehow influences your thinking on this. The MDI buttons are using magic pink trans in the areas that paint darker.

I'm very grateful for the effort you've put in trying to diagnose & resolve my issues, Neil. Wish I could let you have this box for a bit to see what you could do...

First order of business, Nice work Stardock and StardockDesigns
Now I had been running Leo for a while and wanted to use Diamond,
but the Right-Click menu and Program menus are mess up.
I have tried uninstalling/reinstalling didn't work.



Best regards,
Neksus

Neksus,
Could you open the skin folder and delete all files with the extension ".WB4" and then try reapply the skin?
Another action that couls help is check for the latest ATI drivers, the newest is Catalyst 7.7 http://ati.amd.com/support/driver.html

Hey Neil,

Build 27 has fixed the "per application feature disabling". Thanks a ton!

Who should I contact about the Virtual Desktop glitch with the Quick Launch part of the Task-bar? That is still happening - in fact I have turned off VD controlling my wallpaper, and it happens more frequently now.

Sorry for the late reply. Here is the issue with the Sidebar and the Taskbar. Its not much, but it adds a colour mask over the bottom right hand corner where the two meet.

danilloOc
Oh yeah forgot I had already tried deleting the WB4 files, but this time around it fixed it..seems odd to me.

Thanks for the reply

the new v27 fixes the titlebars AND menu/font corruption in Diamond.

Leftover/dangling piece of Start Orb (when autohiding taskbar using Object Dock at top of desktop) still remains, in XP only (on ATI/AMD and Nvidia/Intel machines).

Photoshop 7 seems to crash whenever attempting to open a menu with an image open with WB6 applied in Vista.

Doesn't seem to affect Photoshop CS3, but Filezilla does (latest v3 beta) so maybe they have the same problem.

I can make Filezilla crash if I hit the RMB over any item in any list (Vista 32, WB6, latest beta).

If I select it not to skin in the per application settings, RMB works normally with no crash, so you might want to do that for your photoshop in the interim.

I do notice in CS3 of photoshop that the menu redraw is slow enough that I see it blurring the area then applying. I don't see that in any other program, btw, so that might be where the programmers want to look first. Note that the FileZilla code is open source, they might be able to actually compare code to code and see what precisely is giving these programs and WB6 a headache under Vista.

I hope this helps!

:}

I just tried FileZilla here with the latest WB6 build on Vista and it does not crash when I right click.

What build of WB do you have installed? (see Wbconfig System Information page)

Hi Neil:



see the picture..
my prob still, on vista if enable blur, little white layer left-bottom behind the taskbar..

bilbo1930: that appears to be a bug with the blur system in the DWM

Thanks Neil..

I don't know if anyone saw the above post yet, but I thought I would pass on that the newest build, 5.90(.027, does not resolve the problem.

Neil, You've helped me too. Windowblinds 6 displayed OK in its own window - but none of the clicks caused a new skin to load. Using your recommendation (and rebooting after deleting present installation), the program seems to work just fine. Not that I've exercised all of the potential "tweeks". Thanks, Richard Emery