wxWidgets

“it has enough HTML support for rendering markdown converted to HTML just fine”

“I don't like how wxWidgets look and that touch is seemingly not considered a first-class citizen like mouse+keyboard (yet).”

“I find it very nice to work with compared to attempting to learn any of the myriad UI attempts Microsoft introduced later.”

“It wouldn’t have the drawbacks that they attributed to Qt.”

“You need something like wxWidgets for that, which makes native system calls.”

“It is why the wxWidgets has a license that allows creating monolithic commercial blob dependent binaries for Windows, Linux Gtk/X11, and MacOS.”

“It works very well, and is pretty much the only toolkit to do what it does.”

“It's really unfortunate that they didn't take the opportunity to switch to Qt”

“The old wxWidgets supports native OS interface targeting being truly cross-platform.”

“free wxWidgets native cross platform OS interface support is less hassle”

“have always been robust, stable, well documented, and easy to use”

“wxWidgets comes with a disappointing amount of bloat though.”

“this library has old design written all over it”

“I like that wxWidgets uses native widgets, and is cross-platform”

“If you want to build an app today that will still run in 20 years”

“you can manually construct an interface from nested linear layouts”

“newer toolkits like GTK, Tk, wxWidgets, DWM, Cocoa, etc are great at today”

“wxWidgets is quite great, although I have to also agree with the comment above, that C++ for a GUI library is just a PITA when used from any other language”

“they are very close to native appearances on both macOS and Windows and are much easier to program than anything Qt”

“they tend to not handle DPI scaling well”

“it had a clunky MFC style to it, limited feature, along with a rather Windowsy look and feel”

“It uses the native toolkit no matter where you run it across Windows, GTK, Qt, Motif, macOS/Carbon, macOS/Cocoa, and X11 with generic widgets.”

“MFC, wx, Qt .. it's all overcomplex pointless bloat for this task imo.”

“wxWidgets is also nice, without the licensing weirdness”

“Static linking libraries for MacOS or Windows is contaminated by GPL/LGPL code, and this is why wxwidgets excludes the disclosure requirement.”

“wxWidgets is perhaps the closest we can get where at least you can ask for a wxFindReplaceDialog abstraction”

“wxWidgets has properly supported dark mode for a bit now.”

“wxWidgets seems to translate EXTREMELY well to macOS”

“wxWidgets has sizers where elements sit inside them and grow/shrink as necessary.”

“In wxWidgets you use sizers, so you don't work on pixel-level alignments.”

“wxWidgets uses native controls but they don't behave better despite that.”

“I can still compile it today (if I had the code) against wxWidgets, to then run on macOS and Windows”

“Sometimes outdated versions of those libraries at that.”

“It's the heavy use of C style macros instead of C++ templates, mostly.”

“It's a bit sad that a GUI library absolutely needs to be new and shining to be even considered nowadays”

“Trying to defer to native widget rendering per platform was a mistake”

“none of the Rust toolkits is half as good as the surviving frameworks, like C++ Builder, Qt, wxWidgets”

“feeling somewhat Windowsy though not full-on MFC/Win32”

“For my tastes, the nicest ones were probably GNOME2, Elementary and wxWidgets.”

“Fine for basic interfaces, but static linking on Win64 gets dicey with lgpl libraries etc.”