The tree only sets the focus in response to a TVN_SELCHANGINGW event if the tree...

[wxWidgets.git] / docs / doxygen / groups / funcmacro_debug.h

diff --git a/docs/doxygen/groups/funcmacro_debug.h b/docs/doxygen/groups/funcmacro_debug.h
index 74bc4819f531e9b8a35929029435db85e0876be4..281ba3d13e893ea9ab70e9b59135a2c5c9e6e625 100644 (file)
--- a/docs/doxygen/groups/funcmacro_debug.h
+++ b/docs/doxygen/groups/funcmacro_debug.h
@@ -3,24 +3,24 @@
 // Purpose:     Debugging function and macro group docs
 // Author:      wxWidgets team
 // RCS-ID:      $Id: funcmacro_gdi.h 52454 2008-03-12 19:08:48Z BP $
 // Purpose:     Debugging function and macro group docs
 // Author:      wxWidgets team
 // RCS-ID:      $Id: funcmacro_gdi.h 52454 2008-03-12 19:08:48Z BP $

-// Licence:     wxWindows license
+// Licence:     wxWindows licence

 /////////////////////////////////////////////////////////////////////////////
 
 /**
 
 /////////////////////////////////////////////////////////////////////////////
 
 /**
 

-@defgroup group_funcmacro_debug Debugging
+@defgroup group_funcmacro_debug Debugging macros

 @ingroup group_funcmacro
 
 Useful macros and functions for error checking and defensive programming.
 @ingroup group_funcmacro
 
 Useful macros and functions for error checking and defensive programming.

-wxWidgets defines three families of the assert-like macros: the wxASSERT and
-wxFAIL macros only do anything if __WXDEBUG__ is defined (in other words, in
+wxWidgets defines three families of the assert-like macros: the wxASSERT() and
+wxFAIL() macros only do anything if __WXDEBUG__ is defined (in other words, in

 the debug build) but disappear completely in the release build. On the other
 the debug build) but disappear completely in the release build. On the other

-hand, the wxCHECK macros stay event in release builds but a check failure
-doesn't generate any user-visible effects then. Finally, the compile time
-assertions don't happen during the run-time but result in the compilation error
-messages if the condition they check fail.
+hand, the wxCHECK() macros stay in release builds but a check failure doesn't
+generate any user-visible effects. Finally, the compile time assertions don't
+happen during the run-time but result in the compilation error messages if the
+condition they check fail.

 
 

-@header{wx/debug.h}
+Related class group: @ref group_class_debugging.

 
 */
 
 
 */