So obviously there are currently some issues with the classic theme. This thread is meant to document some of those issues. This post will be updated if/when a fix for an issue is found, or when a new issue is reported or discovered.
Windows 8: Explorer: - The three 'phantom' alt-tab applications (they can be removed with fxxkmetro) - 1px placement issue on the taskbar (only when using ClassicTheme.exe in install mode, other methods do not produce this glitch)
Windows 10: Explorer: - The taskbar appears black with unreadable text, making it quite annoying to use. - Context menus do not display properly. (Fix) - Modern apps. Especially a problem when PC Settings needs to be accessed (can be fixed by starting classic theme after app host).
Windows 8 and Windows 10: Explorer, Paint, Wordpad: - Ribbon does not display correctly
Control Panel Pages that fail to load: - Ease of Access Center - Language - Personalization - Storage Spaces - Work Folders (these can be fixed)
Global Interface Issues - Transparency in some windows. (Fix for Firefox, there are other fix methods)
Could you have been any less specific about that? I'm still not sure what's to blame on the Classic Theme and what's to blame on my Virtual Machine ._.
I know the text and button padding is an issue...is there anything else, though?
Speaking of button padding, I remember reading somewhere that when using metrics from older versions of Windows on Windows 10, the taskbar buttons become pretty wide. This makes me think that Windows 10 interprets that number differently.
Let's say it does produce a larger value on 10 than older versions. That would mean Microsoft must have changed the number to something smaller than its previous value, to counteract this. If this is true, then when Visual Styles are disabled, the old interpretation of the value returns, but since the value is still small, the buttons get crushed together!
Yeah sorry for not being more specific. I'll update that whenever I have the time. Well I'm pretty sure it's an issue with the taskbar and not just a virtual machine, since I was actually running Windows 10 for a while on my computer before my hard drive failed, and I experienced many of the same issues. So the taskbar in Windows 10 needs a lot of work.
is it normal on Classic theme program that when I install it. it breaks Windows Explorer and the control panel that it brings up the classic theme program because things crash on my full copy of Windows 8.1.
Last Edit: May 16, 2016 8:02:07 GMT -8 by bakuchris
I have noticed that with the handle utility method there is no 1-px shift in the taskbar (but the taskbar appears with colored borders). Maybe we could find another way to combat those colored borders than changing dwmapi.dll as the w8classic does? I tried the recent classic shell but the texturing does not work under classic theme.
Well I found it. After using handle utility method, manipulating with styles (setting and removing WS_DLGFRAME) (this can be done using AHK script or Window Detective), the colored borders disappear, only a slightly different color of taskbar is visible (compare to the start button):
ʇǝǝๅ ftw: I really don't get why people find 1909+ a PITA. Most of my setups always run the latest version of Windows because I use a bit of it's functionality (mainly WSL2, the UWP notes app and better Dark Mode support). I've never had any big problems with it
Jan 12, 2021 1:28:31 GMT -8
ʇǝǝๅ ftw: (continuing) that caused me to not want to have Classic Theme on these setups. Can someone explain to me where the bottlenecks in 1909+ are for them and why those bottlenecks are problematic?
Jan 12, 2021 1:29:38 GMT -8
ihatemetro: Vietnamese spam post in General Discussion.
Jan 13, 2021 7:13:44 GMT -8