Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 1
    Out of interest, what do you see as the main problems with WX? Commented Jul 1, 2011 at 11:33
  • 8
    @Tom - poor documentation, especially for the new stuff. The AUI components are barely documented at all with large sections missing, making it difficult to use in a production environment. The documentation for the event process is fundamentally in error with regard to the path that is followed, on win32 at least. Spent a lot of time yelling at the computer, "This should be working!!!" before getting down into the deep processing code to find out that what WX does isn't following the docs and what I was doing would NEVER work. Commented Jul 1, 2011 at 16:57
  • 1
    I was also disturbed by the acceptance of the property grid library into the main line. I used that library and it showed numerous, fundamental design flaws in addition to actual lack of knowledge on behalf of the programmer who wrote it (called virtual functions in constructors for example). It, and the poor state of AUI, showed a trend to poorer standards. I'm also not a big fan of static event tables, though at least there's another way to respond to events...unlike MFC, which WX is just too much like to be exciting anyway. Commented Jul 1, 2011 at 16:59
  • Thanks. I've only used it a bit, and through the wxPython API, where it seemed quite nice. I can appreciate that that would hide some of the evil, but also that i just haven't got deeply enough involved to have come up against the more serious problems. Something for me to be aware of. Commented Jul 1, 2011 at 17:38
  • 2
    everything that responds to a signal has to be a Q_OBJECT, No nowadays... Now, static functions, functions and even lambda functions can respond a signal (you can use function pointers as slots). No-QObject classes can also have member slots if you connect to them using a std::bind to convert the instance member to a function pointer. Commented Mar 1, 2019 at 18:52