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

some HTML links \urlref'ied

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@4522 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
1999-11-12 15:33:47 +00:00
parent e4a71fc3f9
commit 47f7a3a726
2 changed files with 7 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/latex/wx/body.tex
View File

@@ -190,12 +190,9 @@ Metrowerks CodeWarrior.
\section{Availability and location of wxWindows} \section{Availability and location of wxWindows}
wxWindows is available by anonymous FTP and World Wide Web: wxWindows is available by anonymous FTP and World Wide Web
from \urlref{ftp://www.remstar.com/pub/wxwin}{ftp://www.remstar.com/pub/wxwin}
\begin{verbatim} and/or \urlref{http://www.wxwindows.org}{http://www.wxwindows.org}
ftp://www.remstar.com/pub/wxwin
http://www.wxwindows.org
\end{verbatim}
You can also buy a CD-ROM using the form on the Web site, or by contacting: You can also buy a CD-ROM using the form on the Web site, or by contacting:
@@ -727,8 +724,8 @@ See the \helpref{debugging overview}{debuggingoverview} for further information.
\subsection{Check Windows debug messages} \subsection{Check Windows debug messages}
Under Windows, it's worth running your program with DbgView (available from Under Windows, it's worth running your program with
{\tt http://www.sysinternals.com} running or \urlref{DbgView}{http://www.sysinternals.com} running or
some other program that shows Windows-generated debug messages. It's some other program that shows Windows-generated debug messages. It's
possible it'll show invalid handles being used. You may have fun seeing possible it'll show invalid handles being used. You may have fun seeing
what commercial programs cause these normally hidden errors! Microsoft what commercial programs cause these normally hidden errors! Microsoft

4
docs/latex/wx/tlog.tex
View File

@@ -45,8 +45,8 @@ first argument.
does anything at all in the debug mode (when the preprocessor symbol does anything at all in the debug mode (when the preprocessor symbol
\_\_WXDEBUG\_\_ is defined) and expands to nothing in release mode (otherwise). \_\_WXDEBUG\_\_ is defined) and expands to nothing in release mode (otherwise).
{\bf Tip:} under Windows, you must either run the program under debugger or {\bf Tip:} under Windows, you must either run the program under debugger or
use a 3rd party program such as DbgView (from use a 3rd party program such as \urlref{DbgView}{http://www.sysinternals.com}
{\tt http://www.sysinternals.com}) to actually see the debug output. to actually see the debug output.
\item{\bf wxLogTrace} as {\bf wxLogDebug} only does something in debug \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 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 there are a lot of trace messages, so it might make sense to separate them