Guess what, I am 100% sure they do the basic for Win32, make some efforts for WinUI 2.0 (UWP) and WinUI 3.0 (the Win32 one) and that's it.
Guess what, I am 100% sure they do the basic for Win32, make some efforts for WinUI 2.0 (UWP) and WinUI 3.0 (the Win32 one) and that's it.
The Win32 widgets have been updated but apparently they don't want to mess with the metrics, hence those controls are much more compact, don't use rounded corners, etc.
Is there any public UI toolkit in Windows now that offers the canonical widgets?
The WinUI 3.0 (which is UWP decoupled from OS + UI) is still catching up.
https://docs.microsoft.com/en-us/windows/apps/winui/winui2/r...
Thing is, for Win32 anyone using bare bones Win32 has to do the work themselves for anything that ins't on the OS anyway.
So MFC and Forms get a partiall update via those Win32 changes, while WPF gets nothing due to its own DX rendering stack.
https://docs.microsoft.com/en-us/windows/apps/get-started/ma...
In fact already during the Win16 days, many of us were already jumping into C++, Delphi and VB frameworks, instead of suffering through plain C programming.
Borland common controls used to be quite easy to spot with their green check mark.
Win32 has very few built-in controls, and Windows always enjoyed a good ecosystem from commercial vendors selling custom controls, like Telerik and ComponentOne to refer to two well known ones.
As historical info, modern COM traces back to Visual Basic VBX components.
As they pivoted back into Reunion and merging Win32 and UWP worlds, new teams were created, so....
Win32 is quite basic in the set of controls available, almost everything in traditional Win32 applications is custom drawn, beyond what you also find the HTML forms as components.
Then there are all commercial components that are so common in Windows applications.
However if you will, the future is WinUI/UWP, and that is the only one getting full Mica support.