For the first part, I was like, yeah, that’s pretty much how all C++ GUIs work: a markup file describes the structure, a source file controls the behavior, and a special compiler generates more C++ code based on the markup file to act as glue.
That’s all pretty standard, and it’s annoying, but I didn’t really get why they were making such a big deal out of it.
Missing documentation is also annoying but not uncommon for internal widgets.
What really elevates this from simply annoying to transcendentally bad, is the lack of error messages, the undocumented requirements that resource IDs be sequential, and the mandatory IDE plugin. That’s all unforgivable.
For the first part, I was like, yeah, that’s pretty much how all C++ GUIs work: a markup file describes the structure, a source file controls the behavior, and a special compiler generates more C++ code based on the markup file to act as glue.
That’s all pretty standard, and it’s annoying, but I didn’t really get why they were making such a big deal out of it.
Missing documentation is also annoying but not uncommon for internal widgets.
What really elevates this from simply annoying to transcendentally bad, is the lack of error messages, the undocumented requirements that resource IDs be sequential, and the mandatory IDE plugin. That’s all unforgivable.
So you’re saying all C++ GUIs are shit. I concur.
Anti Commercial-AI license
Thats how every GUI which is not immediate mode works. Are there any examples where it works different?