Hacker News Reader

Comment by userbinator | Hacker News Reader

This menu is familiar to me because that’s what the Windows API allows you to create (as long as you are not creating it through Windows Forms.) There is no dark theme for this, but at least there are rounded corners.

That is just a huge WTF. Since the very earliest versions of Windows there has always been the option of a dark (or white, or rainbow, or ...) theme, where you could adjust the colours and sizes and fonts, and everything using Win32 would follow it. Here's Win95 example:

https://64.media.tumblr.com/6d3e8c64cd9a38e70d24c0b1b2c73cb5...

Yet if I'm understanding correctly, in Win11 that stopped working completely? It really sounds like the Windows team has no one left who knows what used to be possible but isn't anymore, being replaced with probably younger developers making constant excuses to "modernise" by rewriting and breaking stuff. To use an analogy, they're not just reinventing the wheel but making it square.

View on HN

> To use an analogy, they're not just reinventing the wheel but making it square.

And then rounding the corners of the said ”wheel” :)

In practice it stopped working well long before windows 11 because so few apps were win32 based and/or because developers would explicitly override the theme. I gave it a go on Windows 7 and even apps like outlook and office wouldn't look right.

Gnome/KDE still offer proper themeing that works with proper native apps but even there you've got web browsers and electron apps that ignore it.

Ah, but you see - there is a difference in how theming works in Windows 11, in that it's different from the high-contrast mode. So, you can get a control that swaps the theme to high-contrast (you need to use the native Windows API for that), but you can't get one that works with the Windows 11 style of dark theme out-of-the-box without re-writing it from zero.

In other words, they decided to rewrite the theme stuff while neglecting to realise that there's existing code (which they mostly broke around the time of Win8 by removing the Appearance control panel...) that would do what they wanted.

I'm in agreement with the others here that Windows 2000 was probably the peak of consistent UI in Windows. XP didn't really regress but added bitmap-style skinning to the elements, and up until 7 the Windows Classic theme was fully customisable. In Win8 they removed that, and it's been a clear downhill from there.

> I'm in agreement with the others here that Windows 2000 was probably the peak of consistent UI in Windows. XP didn't really regress but added bitmap-style skinning to the elements, and up until 7 the Windows Classic theme was fully customisable. In Win8 they removed that, and it's been a clear downhill from there.

I agree almost, but not quite 100% with that. My tiny disagreement: The decline set in a bit earlier, not after but some time in the W7 era: Up until some point you could set window border width to 0 in the Appearance control panel applet; after that this input field was apparently made read-only for the user. For a while after that you could "hack" that by editing a Registry value, but AFAICR they disabled that, too. (Or rather, if not exactly disabled Registry editing, made the display driver ignore it.)

Mind you, at the same time, there's fewer and fewer users for those old features, so why should they be priority vs the people who are just starting to pick up a computer?

The author is pointing out that the context menu style applied through Microsoft's own software GUI framework is inconsistent with the style applied by the rest of the OS. What 'old feature' are you referring to?

Reply on news.ycombinator.com