wxLogChain

This simple class allows to chain log sinks, that is to install a new sink but keep passing log messages to the old one instead of replacing it completely as SetActiveTarget does.

It is especially useful when you want to divert the logs somewhere (for example to a file or a log window) but also keep showing the error messages using the standard dialogs as wxLogGui does by default.

Example of usage:

wxLogChain *logChain = new wxLogChain(new wxLogStderr);

// all the log messages are sent to stderr and also processed as usually
...

// don't delete logChain directly as this would leave a dangling
// pointer as active log target, use SetActiveTarget() instead
delete wxLog::SetActiveTarget(...something else or NULL...);

wxLog

Include files

<wx/log.h>

Members

wxLogChain::wxLogChain
wxLogChain::~wxLogChain
wxLogChain::GetOldLog
wxLogChain::IsPassingMessages
wxLogChain::PassMessages
wxLogChain::SetLog

wxLogChain::wxLogChain

wxLogChain(wxLog *logger)

Sets the specified logger (which may be NULL) as the default log target but the log messages are also passed to the previous log target if any.

wxLogChain::~wxLogChain

~wxLogChain()

Destroys the previous log target.

wxLogChain::GetOldLog

wxLog * GetOldLog() const

Returns the pointer to the previously active log target (which may be NULL).

wxLogChain::IsPassingMessages

bool IsPassingMessages() const

Returns true if the messages are passed to the previously active log target (default) or false if PassMessages had been called.

wxLogChain::PassMessages

void PassMessages(bool passMessages)

By default, the log messages are passed to the previously active log target. Calling this function with false parameter disables this behaviour (presumably temporarily, as you shouldn't use wxLogChain at all otherwise) and it can be reenabled by calling it again with passMessages set to true.

wxLogChain::SetLog

void SetLog(wxLog *logger)

Sets another log target to use (may be NULL). The log target specified in the constructor or in a previous call to this function is deleted.

This doesn't change the old log target value (the one the messages are forwarded to) which still remains the same as was active when wxLogChain object was created.