Inside Qt for Symbian QApplication: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
h2. How is the application started? | h2. How is the application started? | ||
Revision as of 16:04, 3 March 2015
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
h2. How is the application started?
We all know that the application is started after we create a QApplication like the following:
QApplication app(argv, args);<code>
wow, thats really much easier than symbian, you know, you have to know so much about the AVKON application framework when using Symbian C++, and for now, all you have to know is creating a QApplication. But Im the person who always wanna know more, so lets look inside the source code.
First, let us take a look at QApplication's ctor:
QApplication::QApplication(int &argc, char **argv)
: QCoreApplication(*new QApplicationPrivate(argc, argv, GuiClient) //create a QApplicationPrivate
{
Q_D(QApplication); //just Q_D macro, so we can just the following d d->construct(); //call d's construct()
}
Line 2 creates a QApplicationPrivate with argc, argv and GuiClient. Here GuiClient is an enum, and we use it to tell QCoreApplication what type of application we wanna create.