Hi, How does this handle the cases that need code before the QGuiApplication construction? AFAICS it does not.
Laszlo From: Development [mailto:development-bounces+laszlo.agocs=qt...@qt-project.org] On Behalf Of Simon Hausmann Sent: Tuesday, December 13, 2016 10:37 AM To: Mathias Hasselmann <math...@taschenorakel.de>; development@qt-project.org Subject: Re: [Development] A new approach for Qt main() Hi, The joke of the bikeshedding aside I for one do like the idea of exporting a QObject sub-class instead of a function. That makes it easier to extend in the future with more entry-points as slots for example. Simon ________________________________ From: Development <development-bounces+simon.hausmann=qt...@qt-project.org<mailto:development-bounces+simon.hausmann=qt...@qt-project.org>> on behalf of Mathias Hasselmann <math...@taschenorakel.de<mailto:math...@taschenorakel.de>> Sent: Monday, December 12, 2016 7:53:50 PM To: development@qt-project.org<mailto:development@qt-project.org> Subject: Re: [Development] A new approach for Qt main() Hi, Seems this turned into a nice bike shed discussion quickly, so let me use the chance to present my preferred Qt main(). I am totally convinced that this one should rule the Qt world: class BlueBikeShedApplication : public QApplication { Q_OBJECT public: using QApplication::QApplication; int run() { if (!parseCommandLine()) return EXIT_FAILURE; if (!initializeColorBucket()) return EXIT_FAILURE; setupBrush(); return exec(); } }; int main(int argc, char *argv[]) { return BlueBikeShedApplication{argc, argv}.run(); } The big advantage I see in this approach is, that you work within a proper QObject context with fully setup QApplication early. Also this main() is sufficiently generic to be hidden in a platform specific macro, or static library. Thank you for reading, Mathias _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
