5 ms·

Or just plain Win32, no wrappers! Maybe with coding agents it can have a renaissance.

by actionfromafar 9mo ago

pjc50 9mo ago
Annoyingly many of the new features are WinRT only, so you have to deal with that horror. I'm a big fan of the MFC/WinForms era stuff myself, but it has one crippling limitation: it doesn't handle display scaling very well at all.
- pjmlp 9mo ago
  Only AI stuff, there is hardly anything else that depends on WinUI/WinAppSDK. There are Win32 APIs for HiDPI configuration, the issue is that it isn't automatic, it needs to be on the app manifest or called explicitly, and handle the events for resolution changes.
  - pjc50 9mo ago
    Even if you do that, and carefully work in "points" internally rather than pixels, the results seem to be bad. Win32 dialogs are generally not resizable or "responsive". This is even visible in settings dialogs from Windows itself.
    - pjmlp 9mo ago
      Still much better than dealing with WinRT, and its "ATL is great!" attitude, with the endless amount of bugs that never get fixed.
- tcfhgj 9mo ago
  I have been using WinRT and Win32, and I find WinRT much more pleasant to use
  - pjmlp 9mo ago
    Until you will bump into one of those bugs that have been open since Project Reunion was announced.
delta_p_delta_x 9mo ago
> plain Win32 Plain Win32 needs a renaissance. I worked with it and felt like a wizard. Message boxes, dialogue boxes, wizards, hammered out in pure C++. Combined with the Windows Implementation Library[1] I was writing fast, modern code. [1]: https://github.com/microsoft/wil https://github.com/microsoft/wil
- pjmlp 9mo ago
  As side note, WIL was originally introduced for writing drivers in C++ in kernel mode, then expanded to support other workloads on userspace. Here is the original announcement, https://community.osr.com/t/the-new-wil-library-for-c-code-in-drivers/55832 https://community.osr.com/t/the-new-wil-library-for-c-code-i...

5 ms·

Or just plain Win32, no wrappers! Maybe with coding agents it can have a renaissance.

by actionfromafar 9mo ago

Or just plain Win32, no wrappers! Maybe with coding agents it can have a renaissance.

pjc50 9mo ago
Annoyingly many of the new features are WinRT only, so you have to deal with that horror. I'm a big fan of the MFC/WinForms era stuff myself, but it has one crippling limitation: it doesn't handle display scaling very well at all.
- pjmlp 9mo ago
  Only AI stuff, there is hardly anything else that depends on WinUI/WinAppSDK. There are Win32 APIs for HiDPI configuration, the issue is that it isn't automatic, it needs to be on the app manifest or called explicitly, and handle the events for resolution changes.
  - pjc50 9mo ago
    Even if you do that, and carefully work in "points" internally rather than pixels, the results seem to be bad. Win32 dialogs are generally not resizable or "responsive". This is even visible in settings dialogs from Windows itself.
    - pjmlp 9mo ago
      Still much better than dealing with WinRT, and its "ATL is great!" attitude, with the endless amount of bugs that never get fixed.
- tcfhgj 9mo ago
  I have been using WinRT and Win32, and I find WinRT much more pleasant to use
  - pjmlp 9mo ago
    Until you will bump into one of those bugs that have been open since Project Reunion was announced.
delta_p_delta_x 9mo ago
> plain Win32 Plain Win32 needs a renaissance. I worked with it and felt like a wizard. Message boxes, dialogue boxes, wizards, hammered out in pure C++. Combined with the Windows Implementation Library[1] I was writing fast, modern code. [1]: https://github.com/microsoft/wil https://github.com/microsoft/wil
- pjmlp 9mo ago
  As side note, WIL was originally introduced for writing drivers in C++ in kernel mode, then expanded to support other workloads on userspace. Here is the original announcement, https://community.osr.com/t/the-new-wil-library-for-c-code-in-drivers/55832 https://community.osr.com/t/the-new-wil-library-for-c-code-i...