KDECore
#include <kdebug.h>
A class for using operator()
Definition at line 243 of file kdebug.h.
KDebug::KDebug |
( |
QtMsgType |
type, |
|
|
const char * |
f = 0 , |
|
|
int |
l = -1 , |
|
|
const char * |
info = 0 |
|
) |
| |
|
inlineexplicit |
bool KDebug::hasNullOutput |
( |
QtMsgType |
type, |
|
|
bool |
condition, |
|
|
int |
area, |
|
|
bool |
enableByDefault |
|
) |
| |
|
static |
int KDebug::registerArea |
( |
const QByteArray & |
areaName, |
|
|
bool |
enabled = true |
|
) |
| |
|
static |
- Since
- 4.4 Register a debug area dynamically.
- Parameters
-
areaName | the name of the area |
enabled | whether debug output should be enabled by default (users can override this in kdebugdialog or with DisableAll=true in kdebugrc) |
- Returns
- the area code that was allocated for this area
Typical usage: If all uses of the debug area are restricted to a single class, add a method like this (e.g. into the Private class, if there's one) static int debugArea() { static int s_area = KDebug::registerArea("areaName"); return s_area; }
Please do not use a file-static int, it would (indirectly) create KGlobal too early, create KConfig instances too early (breaking unittests which set KDEHOME), etc. By using a function as shown above, you make it all happen on-demand, rather than upfront.
If all uses of the debug area are restricted to a single .cpp file, do the same but outside any class, and then use a more specific name for the function.
If however multiple classes and files need the debug area, then declare it in one file without static, and use "extern int debugArea();" in other files (with a better name for the function of course).
Definition at line 856 of file kdebug.cpp.
The documentation for this class was generated from the following files:
This file is part of the KDE documentation.
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 22:47:10 by
doxygen 1.8.7 written
by
Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.