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

Clarify that QLoggingCategory works independent of compiler build type

Browse Source 
Also mention exception for internal categories starting with 'qt.'

Fixes: QTBUG-93852
Change-Id: Iff8657a31074ee70cba25f6acdccb5ba4b1d3b01
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
Kai Köhne 2021-05-19 15:23:08 +02:00
parent a3c430f390
commit 029425478a
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/corelib/io/qloggingcategory.cpp
View File

@ -124,7 +124,14 @@ static void setBoolLane(QBasicAtomicInt *atomic, bool enable, int shift)
logs messages of type \c QtWarningMsg, \c QtCriticalMsg, \c QtFatalMsg, but
ignores messages of type \c QtDebugMsg and \c QtInfoMsg.
If no argument is passed, all messages are logged.
If no argument is passed, all messages are logged. Only Qt internal categories
which start with \c{qt} are handled differently: For these, only messages of type
\c QtInfoMsg, \c QtWarningMsg, and \c QtCriticalMsg are logged by default.
\note Logging categories are not affected by your C++ build configuration.
That is, whether messages are printed does not change depending on whether
the code is compiled with debug symbols ('Debug Build'), optimizations
('Release Build'), or some other combination.
\section1 Configuring Categories