libkdepim

KPIM::ThreadWeaver Namespace Reference


Classes

class  Event
 A class to represent the events threads generate and send to the Weaver object. More...
class  Job
 A Job is a simple abstraction of an action that is to be executed in a thread context. More...
class  Thread
 The class Thread is used to represent the worker threads in the weaver's inventory. More...
class  Weaver
 A weaver is the manager of worker threads (Thread objects) to which it assigns jobs from it's queue. More...
class  WeaverExtension
 A WeaverExtension can be attached to an existing Weaver object and will then receive signals on actions the Weaver takes, like starting to process a specific job, assigning a job to a thread or suspending a thread. More...
class  WeaverThreadLogger
 A WeaverThreadLogger may be attached to a Weaver to gain debug information about thread execution. More...

Functions

KDE_EXPORT void setDebugLevel (bool debug, int level)
KDE_EXPORT void debug (int severity, const char *cformat,...)

Variables

bool Debug = true
int DebugLevel = 2
KDE_EXPORT bool Debug
KDE_EXPORT int DebugLevel

Variable Documentation

KDE_EXPORT bool KPIM::ThreadWeaver::Debug

This method prints a text message on the screen, if debugging is enabled.

Otherwise, it does nothing. The message is thread safe, therefore providing that the messages appear in the order they where issued by the different threads. All messages are suppressed when Debug is false. All messages with a lower importance (higher number) than DebugLevel will be suppressed, too. Debug level 0 messages will always be printed as long as Debug is true. We use our own debugging method, since debugging threads is a more complicated experience than debugging single threaded contexts. This might change in future in the way that debug prints it's messages to another logging facility provided by the platform. Use setDebugLevel () to integrate adapt debug () to your platform.

Definition at line 28 of file weaver.cpp.

This method prints a text message on the screen, if debugging is enabled.

Otherwise, it does nothing. The message is thread safe, therefore providing that the messages appear in the order they where issued by the different threads. All messages are suppressed when Debug is false. All messages with a lower importance (higher number) than DebugLevel will be suppressed, too. Debug level 0 messages will always be printed as long as Debug is true. We use our own debugging method, since debugging threads is a more complicated experience than debugging single threaded contexts. This might change in future in the way that debug prints it's messages to another logging facility provided by the platform. Use setDebugLevel () to integrate adapt debug () to your platform.

Definition at line 28 of file weaver.cpp.

KDE Home | KDE Accessibility Home | Description of Access Keys