This interface is used to represent the class that can do the actual logging. More...
#include <GCF3/Log>
Public Member Functions | |
virtual void | handleLogMessage (GCF::LogMessage *msg)=0 |
virtual void | print (GCF::LogMessage *msg, QTextStream &ts)=0 |
virtual void | toSupport (const QString &msg) |
virtual void | toClipboard (const QString &msg) |
virtual void | flush () |
Detailed Description
A class that implements this interface can decide the way in which the application logs the different log messages generated in the application via the GCF::Log mechanism. By default GCF::Log implements this interface and logs the messages to an appropriate log file.
You can implement this interface in a class and register it with GCF::Log as the message handler for the application, to control the way in which messages are logged. For example you could write a LogMessageHandler that would write these log messages on to another application via sockets, where the actual logging happens.
Member Function Documentation
|
pure virtual |
|
pure virtual |
|
virtual |
GCF::Log would call this function of the handler with the reported message so that the handler can report the msg
to support.
|
virtual |
GCF::Log would call this function of the handler with the reported message so that the handler can dump msg
to clipboard.
|
virtual |
GCF::Log would call this function of the handler with the reported message so that the handler can perform a flush operation.