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

fixed all doxygen warnings fixable

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@52339 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Francesco Montorsi
2008-03-05 19:08:53 +00:00
parent c1f615bf14
commit 29d21088bb
10 changed files with 350 additions and 275 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/doxygen/mainpages/strategies.h
View File

@@ -54,7 +54,7 @@
@subsection page_strategies_portability_usesizers Use sizers
Don't use absolute panel item positioning if you can avoid it. Different GUIs have
very differently sized panel items. Consider using the @ref overview_sizers instead.
very differently sized panel items. Consider using the @ref overview_sizer instead.
@subsection page_strategies_portability_useresources Use wxWidgets resource files
@@ -102,7 +102,7 @@
@subsection page_strategies_debug_uselogging Use logging functions
There is a variety of logging functions that you can use in your program:
see @ref logfunctions.
see @ref page_func_cat_log.
Using tracing statements may be more convenient than using the debugger
in some circumstances (such as when your debugger doesn't support a lot
@@ -116,7 +116,7 @@
configured. Depending on the operating system and compiler, more or less
specific information about the problem will be logged.
You should also use @ref debugmacros as part of a `defensive programming' strategy,
You should also use @ref page_macro_cat_debugging as part of a `defensive programming' strategy,
scattering wxASSERTs liberally to test for problems in your code as early as possible.
Forward thinking will save a surprising amount of time in the long run.