2 ms·
wxWidgets uses the native OS interfaces. They have a valid point about Qt sometimes breaking things, and should be packaged as an audacity-qt6 fork. Your per
by Joel_Mckay 2mo ago
wxWidgets uses the native OS interfaces. They have a valid point about Qt sometimes breaking things, and should be packaged as an audacity-qt6 fork.
Your perspective is also valid, in that it could be phrased a little kinder. =3
- epcoa 2mo ago> wxWidgets uses the native OS interfaces. Audacity was fooling no one that it was a native MacOS app, or even a particularly well designed GTK app. The fundamental idea of WX is not sound. Turns out MFC is not a great abstraction for AppKit. Even Qt uses some higher level native UI interfaces on its respective implementations.
- torstenvl 2mo agoIn what way is the fundamental idea of wxWidgets not sound? It works very well, and is pretty much the only toolkit to do what it does.
- epcoa 1mo agoTrying to shoe horn multiplatform UI into MFC? Just look at Unicode. It’s an unholy mess. The only toolkit to do what it does? Qt does what it does, even if the approach is not the same (arguably superior), there’s also Tk. There’s also libui and IUP.