1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: Mention further uses of QCA::applicationName()

Browse Source 
Change-Id: I47c72b30d13b8a2b3cfdad262a539a0865a3d635
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Andreas Eliasson <andreas.eliasson@qt.io>
(cherry picked from commit a1b22bc16cdb48f14cbb21b0d5a4662f3692bf62)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Kai Köhne 2023-07-04 08:52:02 +02:00 committed by Qt Cherry-pick Bot
parent 9361271f11
commit 3d21cc29e8
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/corelib/kernel/qcoreapplication.cpp
View File

@ -2666,11 +2666,15 @@ QString QCoreApplication::organizationDomain()
\property QCoreApplication::applicationName
\brief the name of this application
The value is used by the QSettings class when it is constructed
using the empty constructor. This saves having to repeat this
information each time a QSettings object is created.
The application name is used in various Qt classes and modules,
most prominently in \l{QSettings} when it is constructed using the empty constructor.
Other uses are in formatted logging output (see \l{qSetMessagePattern()}),
in output by \l{QCommandLineParser}, in \l{QTemporaryDir} and \l{QTemporaryFile}
default paths, and in some file locations of \l{QStandardPaths}.
\l{Qt D-Bus}, \l{Accessibility}, and the XCB platform integration make use
of the application name, too.
If not set, the application name defaults to the executable name (since 5.0).
If not set, the application name defaults to the executable name.
\sa organizationName, organizationDomain, applicationVersion, applicationFilePath()
*/