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

merged 2.2 branch

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@7748 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2000-07-15 19:51:35 +00:00
parent 8a693e6e04
commit f6bcfd974e
1835 changed files with 237729 additions and 67990 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -29,7 +29,7 @@ appear in a message box by default (but it can be changed, see below). Notice
that the standard behaviour is to not show informational messages if there are
any errors later - the logic being that the later error messages make the
informational messages preceding them meaningless.
\item{\bf wxLogVerbose} is for verbose output. Normally, it's suppressed, but
\item{\bf wxLogVerbose} is for verbose output. Normally, it is suppressed, but
might be activated if the user wishes to know more details about the program
progress (another, but possibly confusing name for the same function is {\bf
wxLogInfo}).
@@ -39,7 +39,7 @@ bar of the active or specified (as the first argument) \helpref{wxFrame}{wxframe
handy for logging errors after system call (API function) failure. It logs the
specified message text as well as the last system error
code ({\it errno} or {\it ::GetLastError()} depending on the platform) and the corresponding error
message. The second form of this function takes the error code explitly as the
message. The second form of this function takes the error code explicitly as the
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
@@ -62,7 +62,7 @@ generic mechanisms, but are not really adapted for wxWindows, while the log
classes are. Some of advantages in using wxWindows log functions are:
\begin{itemize}\itemsep=0pt
\item{\bf Portability} It's a common practice to use {\it printf()} statements or
\item{\bf Portability} It is a common practice to use {\it printf()} statements or
cout/cerr C++ streams for writing out some (debug or otherwise) information.
Although it works just fine under Unix, these messages go strictly nowhere
under Windows where the stdout of GUI programs is not assigned to anything.
@@ -72,7 +72,7 @@ printf()}.
Moreover {\it wxMSW} doesn't have a {\bf console} as you may have with {\it
wxGTK}. Under {\it wxMSW}, a call using {\it cout} just goes nowhere. To
cope with this problem, {\it wxWindows} provides a way to redirect {\it cout}
calls to \helpref{wxTreeCtrl}{wxtreectrl}, {\it i.e.}:
calls to \helpref{wxTextCtrl}{wxtextctrl}, {\it i.e.}:
{\small
\begin{verbatim}
wxLogWindow *logger=new wxLogWindow(your_frame,"Logger");
@@ -109,7 +109,7 @@ After having enumerated all the functions which are normally used to log the
messages, and why would you want to use them we now describe how all this
works.
wxWindows has the notion of a {\it log target}: it's just a class deriving
wxWindows has the notion of a {\it log target}: it is just a class deriving
from \helpref{wxLog}{wxlog}. As such, it implements the virtual functions of
the base class which are called when a message is logged. Only one log target
is {\it active} at any moment, this is the one used by {\it wxLogXXX()}
@@ -136,7 +136,7 @@ stderr by default as its name suggests.
\item{\bf wxLogStream} This class has the same functionality as wxLogStderr,
but uses {\it ostream} and cerr instead of {\it FILE *} and stderr.
\item{\bf wxLogGui} This is the standard log target for wxWindows
applications (it's used by default if you don't do anything) and provides the
applications (it is used by default if you don't do anything) and provides the
most reasonable handling of all types of messages for given platform.
\item{\bf wxLogWindow} This log target provides a "log console" which
collects all messages generated by the application and also passes them to the
@@ -146,7 +146,7 @@ clear the log, close it completely or save all messages to file.
anything. The objects of this class may be instantiated to (temporarily)
suppress output of {\it wxLogXXX()} functions. As an example, trying to open a
non-existing file will usually provoke an error message, but if for some
reasons it's unwanted, just use this construction:
reasons it is unwanted, just use this construction:
{\small
\begin{verbatim}