/**
Creates the log frame window and starts collecting the messages in it.
- @param parent
+ @param pParent
The parent window for the log frame, may be @NULL
- @param title
+ @param szTitle
The title for the log frame
@param show
@true to show the frame initially (default), otherwise
logging them in the log frame (default), @false to only log them in the
log frame.
*/
- wxLogWindow(wxFrame parent, const wxChar title, bool show = true,
+ wxLogWindow(wxWindow* pParent, const wxString& szTitle, bool show = true,
bool passToOld = true);
/**
Called if the user closes the window interactively, will not be
called if it is destroyed for another reason (such as when program
exits).
+
Return @true from here to allow the frame to close, @false to
prevent this from happening.
@see OnFrameDelete()
*/
- virtual bool OnFrameClose(wxFrame frame);
+ virtual bool OnFrameClose(wxFrame* frame);
/**
Called immediately after the log frame creation allowing for
any extra initializations.
*/
- virtual void OnFrameCreate(wxFrame frame);
+ virtual void OnFrameCreate(wxFrame* frame);
/**
Called right before the log frame is going to be deleted: will
always be called unlike OnFrameClose().
*/
- virtual void OnFrameDelete(wxFrame frame);
+ virtual void OnFrameDelete(wxFrame* frame);
/**
Shows or hides the frame.
/**
@class wxLogInterposerTemp
- A special version of wxLogChain which uses itself as the
- new log target. It forwards log messages to the previously installed one in
- addition to
- processing them itself. Unlike wxLogInterposer, it doesn't
- delete the old target which means it can be used to temporarily redirect log
- output.
+ A special version of wxLogChain which uses itself as the new log target.
+ It forwards log messages to the previously installed one in addition to
+ processing them itself. Unlike wxLogInterposer, it doesn't delete the old
+ target which means it can be used to temporarily redirect log output.
As per wxLogInterposer, this class must be derived from to implement
- wxLog::DoLog
- and/or wxLog::DoLogString methods.
+ wxLog::DoLog and/or wxLog::DoLogString methods.
@library{wxbase}
@category{logging}
/**
The default constructor installs this object as the current active log target.
*/
+ wxLogInterposerTemp();
};
/**
Destroys the previous log target.
*/
- ~wxLogChain();
+ virtual ~wxLogChain();
/**
Detaches the old log target so it won't be destroyed when the wxLogChain object
/**
Returns @true if the messages are passed to the previously active log
- target (default) or @false if PassMessages()
- had been called.
+ target (default) or @false if PassMessages() had been called.
*/
bool IsPassingMessages() const;
void PassMessages(bool passMessages);
/**
- Sets another log target to use (may be @NULL). The log target specified
- in the wxLogChain(wxLog*) constructor or in a previous call to
- this function is deleted.
+ Sets another log target to use (may be @NULL).
+
+ The log target specified in the wxLogChain(wxLog*) 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.
Constructs a log target which sends all the log messages to the given
output stream. If it is @NULL, the messages are sent to @c cerr.
*/
- wxLogStream(std::ostream ostr = NULL);
+ wxLogStream(std::ostream *ostr = NULL);
};
@class wxLogStderr
This class can be used to redirect the log messages to a C file stream (not to
- be confused with C++ streams). It is the default log target for the non-GUI
- wxWidgets applications which send all the output to @c stderr.
+ be confused with C++ streams).
+
+ It is the default log target for the non-GUI wxWidgets applications which
+ send all the output to @c stderr.
@library{wxbase}
@category{logging}
Constructs a log target which sends all the log messages to the given
@c FILE. If it is @NULL, the messages are sent to @c stderr.
*/
- wxLogStderr(FILE fp = NULL);
+ wxLogStderr(FILE* fp = NULL);
};
by the new lines.
All the messages collected so far can be shown to the user (and the current
- buffer cleared) by calling the overloaded wxLogBuffer::Flush
- method.
+ buffer cleared) by calling the overloaded wxLogBuffer::Flush method.
@library{wxbase}
@category{logging}
/**
Returns the current buffer contains. Messages from different log function calls
are separated with the new lines in the buffer.
- The buffer can be cleared by Flush() which will
- also show the current contents to the user.
+ The buffer can be cleared by Flush() which will also show the current
+ contents to the user.
*/
- const wxString GetBuffer();
+ const wxString& GetBuffer() const;
};
/**
@class wxLogInterposer
- A special version of wxLogChain which uses itself as the
- new log target. It forwards log messages to the previously installed one in
- addition to
+ A special version of wxLogChain which uses itself as the new log target.
+ It forwards log messages to the previously installed one in addition to
processing them itself.
- Unlike wxLogChain which is usually used directly as is,
- this class must be derived from to implement wxLog::DoLog
- and/or wxLog::DoLogString methods.
+ Unlike wxLogChain which is usually used directly as is, this class must be
+ derived from to implement wxLog::DoLog and/or wxLog::DoLogString methods.
- wxLogInterposer destroys the previous log target in its destructor. If you
- don't want this to happen, use wxLogInterposerTemp instead.
+ wxLogInterposer destroys the previous log target in its destructor.
+ If you don't want this to happen, use wxLogInterposerTemp instead.
@library{wxbase}
@category{logging}
/**
The default constructor installs this object as the current active log target.
*/
+ wxLogInterposer();
};
Constructs a log target which sends all the log messages to the given text
control. The @a textctrl parameter cannot be @NULL.
*/
- wxLogTextCtrl(wxTextCtrl textctrl);
+ wxLogTextCtrl(wxTextCtrl* pTextCtrl);
};
Otherwise, it is completely hidden behind the @e wxLogXXX() functions and
you may not even know about its existence.
- @section overview_wxLog_deriving Deriving your own log target
-
- There are two functions which must be implemented by any derived class to
- actually process the log messages: DoLog() and
- DoLogString(). The second function receives a string
- which just has to be output in some way and the easiest way to write a new log
- target is to override just this function in the derived class. If more control
- over the output format is needed, then the first function must be overridden
- which allows to construct custom messages depending on the log level or even
- do completely different things depending on the message severity (for example,
- throw away all messages except warnings and errors, show warnings on the
- screen and forward the error messages to the user's (or programmer's) cell
- phone - maybe depending on whether the timestamp tells us if it is day or
- night in the current time zone).
- There also functions to support message buffering. Why are they needed?
- Some of wxLog implementations, most notably the standard wxLogGui class,
- buffer the messages (for example, to avoid showing the user a zillion of modal
- message boxes one after another -- which would be really annoying).
- Flush() shows them all and clears the buffer contents.
- This function doesn't do anything if the buffer is already empty.
- See also:
- @li Flush()
- @li FlushActive()
-
- @section overview_wxLog_Trace_Masks Using trace masks
-
- The functions below allow some limited customization of wxLog behaviour
- without writing a new log target class (which, aside from being a matter of
- several minutes, allows you to do anything you want).
- The verbose messages are the trace messages which are not disabled in the
- release mode and are generated by wxLogVerbose(). They
- are not normally shown to the user because they present little interest, but
- may be activated, for example, in order to help the user find some program
- problem.
- As for the (real) trace messages, their handling depends on the settings of
- the (application global) @e trace mask which can either be specified using
- SetTraceMask(), GetTraceMask() and wxLogTrace() which takes an integer mask
- or using AddTraceMask() for string trace masks.
- The difference between bit-wise and string trace masks is that a message using
- integer trace mask will only be logged if all bits of the mask are set in the
- current mask while a message using string mask will be logged simply if the
- mask had been added before to the list of allowed ones.
- For example,
-
- @code
- wxLogTrace( wxTraceRefCount|wxTraceOleCalls, "Active object ref count: %d", nRef );
- @endcode
-
- will do something only if the current trace mask contains both
- @c wxTraceRefCount and @c wxTraceOle, but
-
- @code
- wxLogTrace( wxTRACE_OleCalls, "IFoo::Bar() called" );
- @endcode
-
- will log the message if it was preceded by
-
- @code
- wxLog::AddTraceMask( wxTRACE_OleCalls);
- @endcode
-
- Using string masks is simpler and allows you to easily add custom ones, so this is
- the preferred way of working with trace messages. The integer trace mask is
- kept for compatibility and for additional (but very rarely needed) flexibility
- only.
- The standard trace masks are given in wxLogTrace() documentation.
- Finally, the @e wxLog::DoLog() function automatically prepends a time stamp
- to all the messages. The format of the time stamp may be changed: it can be
- any string with % specifications fully described in the documentation of the
- standard @e strftime() function. For example, the default format is
- "[%d/%b/%y %H:%M:%S] " which gives something like "[17/Sep/98 22:10:16] "
- (without quotes) for the current date. Setting an empty string as the time
- format disables timestamping of the messages completely.
- See also
- @li AddTraceMask()
- @li RemoveTraceMask()
- @li ClearTraceMasks()
- @li GetTraceMasks()
- @li IsAllowedTraceMask()
- @li SetVerbose()
- @li GetVerbose()
- @li SetTimestamp()
- @li GetTimestamp()
- @li SetTraceMask()
- @li GetTraceMask()
- @li SetRepetitionCounting()
- @li GetRepetitionCounting()
-
- @note Timestamping is disabled for Visual C++ users in debug builds by
- default because otherwise it would be impossible to directly go to the line
- from which the log message was generated by simply clicking in the debugger
- window on the corresponding error message. If you wish to enable it, please
- use SetTimestamp() explicitly.
-
- @section overview_wxLog_Target Manipulating the log target
-
- The functions in this section work with and manipulate the active log
- target. The OnLog() is called by the @e wxLogXXX() functions
- and invokes the DoLog() of the active log target if any.
- Get/Set methods are used to install/query the current active target and,
- finally, DontCreateOnDemand() disables the automatic creation of a standard
- log target if none actually exists. It is only useful when the application
- is terminating and shouldn't be used in other situations because it may
- easily lead to a loss of messages. See also
- @li OnLog()
- @li GetActiveTarget()
- @li SetActiveTarget()
- @li DontCreateOnDemand()
- @li Suspend()
- @li Resume()
+ @note For console-mode applications, the default target is wxLogStderr, so
+ that all @e wxLogXXX() functions print on @c stderr when @c wxUSE_GUI = 0.
+
+
+ @section log_derivingyours Deriving your own log target
+
+ There are two functions which must be implemented by any derived class to
+ actually process the log messages: DoLog() and DoLogString().
+ The second function receives a string which just has to be output in some way
+ and the easiest way to write a new log target is to override just this function
+ in the derived class.
+
+ If more control over the output format is needed, then the first function must
+ be overridden which allows to construct custom messages depending on the log level
+ or even do completely different things depending on the message severity
+ (for example, throw away all messages except warnings and errors, show warnings
+ on the screen and forward the error messages to the user's (or programmer's) cell
+ phone - maybe depending on whether the timestamp tells us if it is day or
+ night in the current time zone).
+
+ There also functions to support message buffering. Why are they needed?
+ Some of wxLog implementations, most notably the standard wxLogGui class,
+ buffer the messages (for example, to avoid showing the user a zillion of modal
+ message boxes one after another -- which would be really annoying).
+
+ Flush() shows them all and clears the buffer contents.
+ This function doesn't do anything if the buffer is already empty.
+
+ See also:
+ @li Flush()
+ @li FlushActive()
+
+
+ @section log_tracemasks Using trace masks
+
+ The functions below allow some limited customization of wxLog behaviour
+ without writing a new log target class (which, aside from being a matter of
+ several minutes, allows you to do anything you want).
+ The verbose messages are the trace messages which are not disabled in the
+ release mode and are generated by wxLogVerbose().
+ They are not normally shown to the user because they present little interest,
+ but may be activated, for example, in order to help the user find some program
+ problem.
+
+ As for the (real) trace messages, their handling depends on the settings of
+ the (application global) @e trace mask which can either be specified using
+ SetTraceMask(), GetTraceMask() and wxLogTrace() which takes an integer mask
+ or using AddTraceMask() for string trace masks.
+
+ The difference between bit-wise and string trace masks is that a message using
+ integer trace mask will only be logged if all bits of the mask are set in the
+ current mask while a message using string mask will be logged simply if the
+ mask had been added before to the list of allowed ones.
+ For example,
+
+ @code
+ wxLogTrace( wxTraceRefCount|wxTraceOleCalls, "Active object ref count: %d", nRef );
+ @endcode
+
+ will do something only if the current trace mask contains both @c wxTraceRefCount
+ and @c wxTraceOle, but:
+
+ @code
+ wxLogTrace( wxTRACE_OleCalls, "IFoo::Bar() called" );
+ @endcode
+
+ will log the message if it was preceded by:
+
+ @code
+ wxLog::AddTraceMask( wxTRACE_OleCalls);
+ @endcode
+
+ Using string masks is simpler and allows you to easily add custom ones, so this
+ is the preferred way of working with trace messages. The integer trace mask is
+ kept for compatibility and for additional (but very rarely needed) flexibility
+ only.
+
+ The standard trace masks are given in wxLogTrace() documentation.
+
+ Finally, the @e wxLog::DoLog() function automatically prepends a time stamp
+ to all the messages. The format of the time stamp may be changed: it can be
+ any string with % specifications fully described in the documentation of the
+ standard @e strftime() function. For example, the default format is
+ "[%d/%b/%y %H:%M:%S] " which gives something like "[17/Sep/98 22:10:16] "
+ (without quotes) for the current date. Setting an empty string as the time
+ format or calling the shortcut wxLog::DisableTimestamp(), disables timestamping
+ of the messages completely.
+
+ See also
+ @li AddTraceMask()
+ @li RemoveTraceMask()
+ @li ClearTraceMasks()
+ @li GetTraceMasks()
+ @li IsAllowedTraceMask()
+ @li SetVerbose()
+ @li GetVerbose()
+ @li SetTimestamp()
+ @li GetTimestamp()
+ @li SetTraceMask()
+ @li GetTraceMask()
+ @li SetRepetitionCounting()
+ @li GetRepetitionCounting()
+
+ @note
+ Timestamping is disabled for Visual C++ users in debug builds by
+ default because otherwise it would be impossible to directly go to the line
+ from which the log message was generated by simply clicking in the debugger
+ window on the corresponding error message. If you wish to enable it, please
+ use SetTimestamp() explicitly.
+
+
+ @section log_target Manipulating the log target
+
+ The functions in this section work with and manipulate the active log
+ target. The OnLog() is called by the @e wxLogXXX() functions
+ and invokes the DoLog() of the active log target if any.
+
+ Get/Set methods are used to install/query the current active target and,
+ finally, DontCreateOnDemand() disables the automatic creation of a standard
+ log target if none actually exists. It is only useful when the application
+ is terminating and shouldn't be used in other situations because it may
+ easily lead to a loss of messages.
+
+ See also:
+ @li OnLog()
+ @li GetActiveTarget()
+ @li SetActiveTarget()
+ @li DontCreateOnDemand()
+ @li Suspend()
+ @li Resume()
+
@library{wxcore}
@category{logging}
{
public:
/**
- Add the @a mask to the list of allowed masks for
- wxLogTrace().
+ Add the @a mask to the list of allowed masks for wxLogTrace().
@see RemoveTraceMask(), GetTraceMasks()
*/
static void AddTraceMask(const wxString& mask);
/**
- Removes all trace masks previously set with
- AddTraceMask().
+ Removes all trace masks previously set with AddTraceMask().
@see RemoveTraceMask()
*/
static void ClearTraceMasks();
- /**
- Disables time stamping of the log messages.
- This function is new since wxWidgets version 2.9
- */
- void SetTimestamp(const wxString& format);
-
- /**
- Called to process the message of the specified severity. @a msg is the text
- of the message as specified in the call of @e wxLogXXX() function which
- generated it and @a timestamp is the moment when the message was generated.
- The base class version prepends the timestamp to the message, adds a prefix
- corresponding to the log level and then calls
- DoLogString() with the resulting string.
- */
- virtual void DoLog(wxLogLevel level, const wxString& msg,
- time_t timestamp);
-
- /**
- Called to log the specified string. The timestamp is already included in the
- string but still passed to this function.
- A simple implementation may just send the string to @c stdout or, better,
- @c stderr.
- */
- virtual void DoLogString(const wxString& msg, time_t timestamp);
-
/**
Instructs wxLog to not create new log targets on the fly if there is none
currently. (Almost) for internal use only: it is supposed to be called by the
application shutdown code.
- Note that this function also calls
- ClearTraceMasks().
+
+ Note that this function also calls ClearTraceMasks().
*/
static void DontCreateOnDemand();
/**
- Shows all the messages currently in buffer and clears it. If the buffer
- is already empty, nothing happens.
+ Shows all the messages currently in buffer and clears it.
+ If the buffer is already empty, nothing happens.
*/
virtual void Flush();
static const wxString GetTimestamp();
/**
- Returns the current trace mask, see Customization() section
- for details.
+ Returns the current trace mask, see Customization() section for details.
*/
static wxTraceMask GetTraceMask();
static bool GetVerbose();
/**
- Returns @true if the @a mask is one of allowed masks for
- wxLogTrace().
-
+ Returns @true if the @a mask is one of allowed masks for wxLogTrace().
+
See also: AddTraceMask(), RemoveTraceMask()
*/
static bool IsAllowedTraceMask(const wxString& mask);
- /**
- There are two functions which must be implemented by any derived class to
- actually process the log messages: DoLog() and
- DoLogString(). The second function receives a string
- which just has to be output in some way and the easiest way to write a new log
- target is to override just this function in the derived class. If more control
- over the output format is needed, then the first function must be overridden
- which allows you to construct custom messages depending on the log level or even
- do completely different things depending on the message severity (for example,
- throw away all messages except warnings and errors, show warnings on the
- screen and forward the error messages to the user's (or programmer's) cell
- phone - maybe depending on whether the timestamp tells us if it is day or
- night in the current time zone).
- There also functions to support message buffering. Why are they needed?
- Some of wxLog implementations, most notably the standard wxLogGui class,
- buffer the messages (for example, to avoid showing the user a zillion of modal
- message boxes one after another -- which would be really annoying).
- Flush() shows them all and clears the buffer contents.
- This function doesn't do anything if the buffer is already empty.
- Flush()
-
- FlushActive()
- */
-
-
/**
Forwards the message at specified level to the @e DoLog() function of the
active log target if there is any, does nothing otherwise.
/**
Remove the @a mask from the list of allowed masks for
wxLogTrace().
- See also: AddTraceMask()
+
+ @see AddTraceMask()
*/
static void RemoveTraceMask(const wxString& mask);
static void SetTimestamp(const wxString& format);
/**
- Sets the trace mask, see Customization()
- section for details.
+ Disables time stamping of the log messages.
+
+ @since 2.9.0
+ */
+ static void DisableTimestamp();
+
+ /**
+ Sets the trace mask, see @ref log_derivingyours section for details.
*/
static void SetTraceMask(wxTraceMask mask);
static void SetVerbose(bool verbose = true);
/**
- Suspends the logging until Resume() is called. Note that
- the latter must be called the same number of times as the former to undo it,
- i.e. if you call Suspend() twice you must call Resume() twice as well.
+ Suspends the logging until Resume() is called.
+
+ Note that the latter must be called the same number of times as the former
+ to undo it, i.e. if you call Suspend() twice you must call Resume() twice as well.
+
Note that suspending the logging means that the log sink won't be be flushed
periodically, it doesn't have any effect if the current log target does the
- logging immediately without waiting for Flush() to be
- called (the standard GUI log target only shows the log dialog when it is
- flushed, so Suspend() works as expected with it).
+ logging immediately without waiting for Flush() to be called (the standard
+ GUI log target only shows the log dialog when it is flushed, so Suspend()
+ works as expected with it).
@see Resume(), wxLogNull
*/
static void Suspend();
+
+protected:
+
+ /**
+ Called to process the message of the specified severity. @a msg is the text
+ of the message as specified in the call of @e wxLogXXX() function which
+ generated it and @a timestamp is the moment when the message was generated.
+
+ The base class version prepends the timestamp to the message, adds a prefix
+ corresponding to the log level and then calls
+ DoLogString() with the resulting string.
+ */
+ virtual void DoLog(wxLogLevel level, const wxString& msg, time_t timestamp);
+
+ /**
+ Called to log the specified string. The timestamp is already included in the
+ string but still passed to this function.
+
+ A simple implementation may just send the string to @c stdout or, better,
+ @c stderr.
+ */
+ virtual void DoLogString(const wxString& msg, time_t timestamp);
};
For instance, the example of the overview:
@code
- wxFile file;
+ wxFile file;
// wxFile.Open() normally complains if file can't be opened, we don't want it
{
would be better written as:
@code
- wxFile file;
+ wxFile file;
// don't try to open file if it doesn't exist, we are prepared to deal with
// this ourselves - but all other errors are not expected
/**
Resumes logging.
*/
+ ~wxLogNull();
};
projects / wxWidgets.git / blobdiff