Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mention log components in wxLogTrace() documentation.

Browse Source 
Using different log components for different logging statements provides a
better (because more general and efficient) way to do the same thing that
wxLogTrace() does, so mention them when describing wxLogTrace().

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@62348 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2009-10-09 13:04:44 +00:00
parent b38dc31ffa
commit 7bfc10389a
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
interface/wx/log.h
View File

@@ -633,6 +633,11 @@ public:
@section log_tracemasks Using trace masks @section log_tracemasks Using trace masks
Notice that the use of log trace masks is hardly necessary any longer in
current wxWidgets version as the same effect can be achieved by using
different log components for different log statements of any level. Please
see @ref overview_log_enable for more information about the log components.
The functions below allow some limited customization of wxLog behaviour The functions below allow some limited customization of wxLog behaviour
without writing a new log target class (which, aside from being a matter of without writing a new log target class (which, aside from being a matter of
several minutes, allows you to do anything you want). several minutes, allows you to do anything you want).
@@ -1257,6 +1262,13 @@ void wxVLogError(const char* formatString, va_list argPtr);
/** @addtogroup group_funcmacro_log */ /** @addtogroup group_funcmacro_log */
//@{ //@{
/** /**
Log a message at wxLOG_Trace log level.
Notice that the use of trace masks is not recommended any more as setting
the log components (please see @ref overview_log_enable) provides a way to
do the same thing for log messages of any level, and not just the tracing
ones.
Like wxLogDebug(), trace functions only do something in debug builds and Like wxLogDebug(), trace functions only do something in debug builds and
expand to nothing in the release one. The reason for making it a separate expand to nothing in the release one. The reason for making it a separate
function is that usually there are a lot of trace messages, so it might function is that usually there are a lot of trace messages, so it might