removed wxAcceleratorTable copy ctor docs, no port implements it

[wxWidgets.git] / docs / doxygen / mainpages / strategies.h

diff --git a/docs/doxygen/mainpages/strategies.h b/docs/doxygen/mainpages/strategies.h
index 4ab1119dc0765ec88fbbd10e57bfcb6b33b453cf..b9ff2c212d77468ec827a36e5d10052cdc8b9f36 100644 (file)
--- a/docs/doxygen/mainpages/strategies.h
+++ b/docs/doxygen/mainpages/strategies.h
@@ -7,7 +7,7 @@
 /////////////////////////////////////////////////////////////////////////////
 
 
 /////////////////////////////////////////////////////////////////////////////
 
 

-/*!
+/**

 
  @page page_strategies Programming strategies
 
 
  @page page_strategies Programming strategies
 


@@ -54,12 +54,12 @@
  @subsection page_strategies_portability_usesizers Use sizers
 
  Don't use absolute panel item positioning if you can avoid it. Different GUIs have
  @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 sizer_overview instead.
+ very differently sized panel items. Consider using the @ref overview_sizer instead.

 
  @subsection page_strategies_portability_useresources Use wxWidgets resource files
 
  Use .xrc (wxWidgets resource files) where possible, because they can be easily changed
 
  @subsection page_strategies_portability_useresources Use wxWidgets resource files
 
  Use .xrc (wxWidgets resource files) where possible, because they can be easily changed

- independently of source code. See the @ref xrc_overview for more info.
+ independently of source code. See the @ref overview_xrc for more info.

 
 
 
 
 
 


@@ -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:
  @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
 
  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,10 +116,10 @@
  configured. Depending on the operating system and compiler, more or less
  specific information about the problem will be logged.
 
  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.
 
  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.
 

- See the @ref debugging_overview for further information.
+ See the @ref overview_debugging for further information.

 
 */
 
 */