qt5.12官方文档： https://doc.qt.io/qt-5/qapplication.html#details ，文档上讲解的比较全面。 下面几个地方需要注意：
A global pointer referring to the unique application object. It is equivalent to QCoreApplication::instance(), but cast as a QApplication pointer, so only valid when the unique application object is a QApplication.
“For any GUI application using Qt, there is precisely one QApplication object, no matter whether the application has 0, 1, 2 or more windows at any given time. For non-QWidget based Qt applications, use QGuiApplication instead, as it does not depend on the QtWidgets library”
3） QApplication's main areas of responsibility are:
- It initializes the application with the user's desktop settings such as palette(), font() and doubleClickInterval(). It keeps track of these properties in case the user changes the desktop globally, for example through some kind of control panel.
- It performs event handling, meaning that it receives events from the underlying window system and dispatches them to the relevant widgets. By using sendEvent() and postEvent() you can send your own events to widgets.
- It parses common command line arguments and sets its internal state accordingly. See the constructor documentation below for more details.
- It defines the application's look and feel, which is encapsulated in a QStyle object. This can be changed at runtime with setStyle().
- It specifies how the application is to allocate colors. See setColorSpec() for details.
- It provides localization of strings that are visible to the user via translate().
- It provides some magical objects like the desktop() and the clipboard().
- It knows about the application's windows. You can ask which widget is at a certain position using widgetAt(), get a list of topLevelWidgets() and closeAllWindows(), etc.
- It manages the application's mouse cursor handling, see setOverrideCursor()
4) QApplication 对象要先于其他对象创建
Since the QApplication object does so much initialization, it must be created before any other objects related to the user interface are created. QApplication also deals with common command line arguments. Hence, it is usually a good idea to create it before any interpretation or modification of
argv is done in the application itself.(该类需要接受命令行参数)
autoSipEnabled ：Set this property to true to automatically display the SIP when entering widgets that accept keyboard input.
doubleClickInterval : This property holds the time limit in milliseconds that distinguishes a double click from two consecutive mouse clicks
startDragDistance : If you support drag and drop in your application, and want to start a drag and drop operation after the user has moved the cursor a certain distance with a button held down, you should use this property's value as the minimum distance required.
QApplication::QApplication(int &argc, char **argv)
Initializes the window system and constructs an application object with argc command line arguments in argv.
Warning: The data referred to by argc and argv must stay valid for the entire lifetime of the QApplication object. In addition, argc must be greater than zero and argv must contain at least one valid character string.
qApp pointer refers to this application object. Only one application object should be created.
This application object must be constructed before any paint devices (including widgets, pixmaps, bitmaps etc.).
Note: argc and argv might be changed as Qt removes command line arguments that it recognizes.
It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets.
Generally, no user interaction can take place before calling exec(). As a special case, modal widgets like QMessageBox can be used before calling exec(), because modal widgets call exec() to start a local event loop.
To make your application perform idle processing, i.e., executing a special function whenever there are no pending events, use a QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
We recommend that you connect clean-up code to the aboutToQuit() signal, instead of putting it in your application's
main() function. This is because, on some platforms the QApplication::exec() call may not return. For example, on the Windows platform, when the user logs off, the system terminates the process after Qt closes all top-level windows. Hence, there is no guarantee that the application will have time to exit its event loop and execute code at the end of the
main() function, after the QApplication::exec() call.