mjdbb1

mjdbb1

Joined Member # 3992845
1 Posts 3 Replies 357 Reputation

You can't exclude Classic Shell because it resides in explorer.exe. A better question is, why does WB have to take over font settings, especially when it's own built-in font settings barely work correctly?

7 Replies 10,113 Views

I've been trying out WindowBlinds on Windows 8 to try to get an Aero-like experience. The 'Win8' theme is very good, however when I use Classic Shell, the right column of the start menu has black text instead of white. If I unload WindowBlinds, the text goes back to white like it should be. I've discussed this over on the Classic Shell forums and have tried tweaking that program but WindowBlinds always takes over and changes the text to black. It make

7 Replies 10,113 Views

And not to hijack my own post, but in Windows 8.1 whenever WB is loaded and you right-click on the desktop, the menu is always in Arial instead of SegoeUI...a minor issue, sure, but it happens no matter what skin I choose. I've tried to adjust the Font settings through WB but nothing changes that.

173 Replies 476,249 Views

1) Classic Shell 2) Windows 8.1 3) "Win8" 4) The right column of the start menu text is black instead of white. As soon as you unload WindowBlinds it goes back to the normal white. This happens in a few other skins as well (i.e. Corporate) so it may be a skin issue. Either way the start menu is very difficult to read in black. By the way, I know about Start8, and I would use that instead...if only it could do the fly-out menus for All Programs

173 Replies 476,249 Views