#include <mxmStatusMessageHandlerInterface.h>
Inheritance diagram for mxmStatusMessageHandlerInterface:
Public Member Functions | |
virtual void | sendStatusMessage (mxm::StatusMessageType msg_type, const mxmString &msg, const mxmObject *sending_object=0)=0 |
Processes the status message as it sees it fit. | |
virtual void | setStatusMessageVerbosity (mxm::StatusMessageType msg_level)=0 |
Used (e.g. | |
virtual mxm::StatusMessageType | statusMessageVerbosity ()=0 |
Returns the verbosity level currently supported/expected by the handler. |
An installed custom status message handler could for example output the messages to a nifty GUI widget.
[khe]
Kai Hergenroether
|
Processes the status message as it sees it fit. Note that implementations for multithreaded environments need to be thread safe! Implemented in mxmNopStatusMessageHandler, and mx::FrameworkMessageHandler. |
|
Used (e.g. by the central status message facility) to switch the handler to a given verbosity level - the handler is free to ignore the request, though. Implemented in mxmNopStatusMessageHandler, and mx::FrameworkMessageHandler. |
|
Returns the verbosity level currently supported/expected by the handler. Through the return value the handler tells the calling context (the central status message facility, and thus application code) which status messages it is interested in. By returning sensible values it can help application code to reduce overhead by only composing status messages that are actually needed. Application code can use mxm::statusMessageUseful() to determine whether or not a message for a given level is currently useful. Implemented in mxmNopStatusMessageHandler, and mx::FrameworkMessageHandler. |