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
This commit is contained in:
@@ -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
|
||||
|
Reference in New Issue
Block a user