Still not seeing any fix.
from
WinCustomize Forums
Here's what the history tells me in WB5 (beta), this is the one before the last build (5.00.005):
WB 5.00 refresh beta
--------------------------
Some bug hunting based on user feedback.
-Fix for Clipmate 7 explorer toolbar addin casing taskbar flicker
-Excluded Clipmate 7 ownerdrawn menus
-Fixed maximized MDI child buttons showing classic buttons
-Fix for apps sometimes turning black with multiple/varied per app skins
-Shellstyle colour masks (rarely used), were not being used.
-Fix for Galciv2 + boundchecker + running the debugger
-Replaced skin database for now with a flat file to deal with
the people reporting ODBC driver issues.
-Prompts for people where were running cracked versions
of the WindowBlinds 5 betas to remove the regkeys that they
were trying to bypass product activation with so things work. This
was preventing wbconfig from loading at all.
-No fixes for people using anti-Windows Product Activation hacks (antiwpa.dll)
Still looking into the ActiveWords reports.
Line three (3) states that the problem with MDI child buttons showing classic is fixed. I can't seem to make any skins show this fix, still seeing the classic buttons. I have been making a skin for the last month, and most of that time, I was trying to figure out why the MDI's buttons weren't appearing. Then I notice that others had the same problem. I've applied Cyclops, the latest skin built for WB5 that I know has MDI buttons-and they don't show. What gives??? That whole bar isn't getting skinned, however menus off that bar do. Can we get a fix for this? I know it's a small thing, but it has driven me coo-coo. Thanks in advance.