OutputDebugStringW95 removed - it's really unnecessary - and the references to

DBWIN32 in the docs replaced with DbgView


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@4520 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/latex/wx/body.tex

@@ -727,7 +727,8 @@ See the \helpref{debugging overview}{debuggingoverview} for further information.
 
 \subsection{Check Windows debug messages}
 
-Under Windows, it's worth running your program with DBWIN running or
+Under Windows, it's worth running your program with DbgView (available from
+{\tt http://www.sysinternals.com} running or
 some other program that shows Windows-generated debug messages. It's
 possible it'll show invalid handles being used. You may have fun seeing
 what commercial programs cause these normally hidden errors! Microsoft

docs/latex/wx/function.tex

@@ -1022,6 +1022,8 @@ See also \helpref{wxDDEServer}{wxddeserver}, \helpref{wxDDEClient}{wxddeclient},
 
 \func{void}{wxDebugMsg}{\param{const wxString\& }{fmt}, \param{...}{}}
 
+{\bf This function is deprecated, use \helpref{wxLogDebug}{wxlogoverview} instead!}
+
 Display a debugging message; under Windows, this will appear on the
 debugger command window, and under Unix, it will be written to standard
 error.
@@ -1029,10 +1031,6 @@ error.
 The syntax is identical to {\bf printf}: pass a format string and a
 variable list of arguments.
 
-Note that under Windows, you can see the debugging messages without a
-debugger if you have the DBWIN debug log application that comes with
-Microsoft C++.
-
 {\bf Tip:} under Windows, if your application crashes before the
 message appears in the debugging window, put a wxYield call after
 each wxDebugMsg call. wxDebugMsg seems to be broken under WIN32s

docs/latex/wx/tlog.tex

@@ -44,6 +44,9 @@ first argument.
 \item{\bf wxLogDebug} is {\bf the} right function for debug output. It only
 does anything at all in the debug mode (when the preprocessor symbol
 \_\_WXDEBUG\_\_ is defined) and expands to nothing in release mode (otherwise).
+{\bf Tip:} under Windows, you must either run the program under debugger or
+use a 3rd party program such as DbgView (from 
+{\tt http://www.sysinternals.com}) to actually see the debug output.
 \item{\bf wxLogTrace} as {\bf wxLogDebug} only does something in debug
 build. The reason for making it a separate function from it is that usually
 there are a lot of trace messages, so it might make sense to separate them