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

Fixed some .tex problems

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@752 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
1998-09-18 10:20:32 +00:00
parent 9b6dbb0974
commit 2319d2b09a
4 changed files with 13 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/latex/wx/classes.tex
View File

@@ -99,7 +99,7 @@ $$\image{14cm;0cm}{wxclass.ps}$$
\input listbox.tex \input listbox.tex
\input listctrl.tex \input listctrl.tex
\input listevt.tex \input listevt.tex
\input log.tex %\input log.tex
\input mask.tex \input mask.tex
\input mdi.tex \input mdi.tex
\input menu.tex \input menu.tex

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

@@ -2,9 +2,7 @@
wxConfigBase class defines the basic interface of all config classes. It can wxConfigBase class defines the basic interface of all config classes. It can
not be used by itself (it's an abstract base class) and you'll always use one not be used by itself (it's an abstract base class) and you'll always use one
of its derivations: \helpref{wxIniConfig}{wxiniconfig}, of its derivations: wxIniConfig, wxFileConfig, wxRegConfig or any other.
\helpref{wxFileConfig}{wxfileconfig}, \helpref{wxRegConfig}{wxregconfig} or
any other.
However, usually you don't even need to know the precise nature of the class However, usually you don't even need to know the precise nature of the class
you're working with but you would just use the wxConfigBase methods. This you're working with but you would just use the wxConfigBase methods. This

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

@@ -1,7 +1,7 @@
\section{Log classes overview}\label{wxlogoverview} \section{Log classes overview}\label{wxlogoverview}
Classes: \helpref{wxLog}wxlog, \helpref{wxLogStderr}wxlogstderr, Classes: \helpref{wxLog}{wxlog}, \helpref{wxLogStderr}{wxlogstderr},
\helpref{wxLogOstream}wxlogostream, \helpref{wxLogTextCtrl}wxlogtextctrl, \helpref{wxLogOstream}{wxlogostream}, \helpref{wxLogTextCtrl}{wxlogtextctrl},
\helpref{wxLogWindow}{wxlogwindow}, \helpref{wxLogGui}{wxloggui}, \helpref{wxLogWindow}{wxlogwindow}, \helpref{wxLogGui}{wxloggui},
\helpref{wxLogNull}{wxlognull} \helpref{wxLogNull}{wxlognull}
@@ -16,51 +16,43 @@ First of all, no knowledge of {\it wxLog} classes is needed to use them. For
this, you should only know about {\it wxLogXXX()} functions. All of them have this, you should only know about {\it wxLogXXX()} functions. All of them have
the same syntax as {\it printf()}, i.e. they take the format string as the the same syntax as {\it printf()}, i.e. they take the format string as the
first argument and a variable number of arguments. Here are all of them: first argument and a variable number of arguments. Here are all of them:
\begin{itemize}\itemsep=0pt \begin{itemize}\itemsep=0pt
\item{\bf wxLogFatalError} which is like {\it wxLogError}, but also \item{\bf wxLogFatalError} which is like {\it wxLogError}, but also
terminates the program with the exit code 3 (using {\it abort()} standard terminates the program with the exit code 3 (using {\it abort()} standard
function also terminates the program with this exit code). function also terminates the program with this exit code).
\item{\bf wxLogError} is the function to use for error messages, i.e. the \item{\bf wxLogError} is the function to use for error messages, i.e. the
messages that must be shown to the user. The default processing is to pop up a messages that must be shown to the user. The default processing is to pop up a
message box to inform the user about it. message box to inform the user about it.
\item{\bf wxLogWarning} for warnings - they are also normally shown to the \item{\bf wxLogWarning} for warnings - they are also normally shown to the
user, but don't interrupt the program work. user, but don't interrupt the program work.
\item{\bf wxLogMessage} is for all normal, informational messages. They also \item{\bf wxLogMessage} is for all normal, informational messages. They also
appear in a message box by default (but it can be changed, see below). Notice 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 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 any errors later - the logic being that the later error messages make the
informational messages preceding them meaningless. 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's suppressed, but
might be activated if the user wishes to know more details about the program 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 progress (another, but possibly confusing name for the same function is {\bf
wxLogInfo} wxLogInfo}
\item{\bf wxLogStatus} is for status messages - they will go into the status \item{\bf wxLogStatus} is for status messages - they will go into the status
bar of the active or specified (as the first argument) bar of the active or specified (as the first argument)
\helpref{wxFrame}{wxframe} if it has one. \helpref{wxFrame}{wxframe} if it has one.
\item{\bf wxLogSysError} is mostly used by wxWindows itself, but might be \item{\bf wxLogSysError} is mostly used by wxWindows itself, but might be
handy for logging errors after system call (API function) failure. It logs the 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 specified message text as well as the last system error code ({\it errno} or
{\it ::GetLastError()} depending on the platform) and the corresponding error {\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 explitly as the
first argument. first argument.
\item{\bf wxLogDebug} is {\bf the} right function for debug output. It only \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 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).
\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
from other debug messages which would be flooded in them. Moreover, the second from other debug messages which would be flooded in them. Moreover, the second
version of this function takes a trace mask as the first argument which allows version of this function takes a trace mask as the first argument which allows
to further restrict the amount of messages generated. to further restrict the amount of messages generated.
\end{itemize} \end{itemize}
% VZ: Julian, am I pushing too much here? % VZ: Julian, am I pushing too much here?
@@ -69,22 +61,20 @@ be asked why not use the other logging facilities, such as C standard stdio
functions or C++ streams. The short answer is that they're all very good functions or C++ streams. The short answer is that they're all very good
generic mechanisms, but are not really adapted for wxWindows, while the log generic mechanisms, but are not really adapted for wxWindows, while the log
classes are. Some of advantages in using wxWindows log functions are: classes are. Some of advantages in using wxWindows log functions are:
\begin{itemize}\itemsep=0pt
\begin{itemize}\itemsep=0pt
\item{Portability} It's a common practice to use {\it printf()} statements or \item{Portability} It's a common practice to use {\it printf()} statements or
cout/cerr C++ streams for writing out some (debug or otherwise) information. cout/cerr C++ streams for writing out some (debug or otherwise) information.
Although it works just fine under Unix, these messages go strictly nowever Although it works just fine under Unix, these messages go strictly nowever
under Windows where the stdout of GUI programs is not assigned to anything. under Windows where the stdout of GUI programs is not assigned to anything.
Thus, you might view {\it wxLogMessage()} as a simple substitute for {\it Thus, you might view {\it wxLogMessage()} as a simple substitute for {\it
printf()}. printf()}.
\item{Flexibility} The output of wxLog functions can be redirected or \item{Flexibility} The output of wxLog functions can be redirected or
suppressed entirely based on their importance, which is either impossible or suppressed entirely based on their importance, which is either impossible or
difficult to do with traditional methods. For example, only error messages, or difficult to do with traditional methods. For example, only error messages, or
only error messages and warnings might be logged, filtering out all only error messages and warnings might be logged, filtering out all
informational messages. informational messages.
\item{Completeness} Usually, an error message should be presented to the user
\item{Comlpeteness} Usually, an error message should be presented to the user
when some operation fails. Let's take a quite simple but common case of a file when some operation fails. Let's take a quite simple but common case of a file
error: suppose that you're writing your data file on disk and there is not error: suppose that you're writing your data file on disk and there is not
enough space. The actual error might have been detected inside wxWindows code enough space. The actual error might have been detected inside wxWindows code
@@ -94,7 +84,6 @@ written to the disk. However, as wxWindows uses {\it wxLogError()} in this
situation, the exact error code (and the corresponding error message) will be situation, the exact error code (and the corresponding error message) will be
given to the user together with "high level" message about data file writing given to the user together with "high level" message about data file writing
error. error.
\end{itemize} \end{itemize}
After having enumerated all the functions which are normally used to log the After having enumerated all the functions which are normally used to log the
@@ -121,27 +110,26 @@ types yourself.
There are some predefined classes deriving from wxLog and which might be There are some predefined classes deriving from wxLog and which might be
helpful to see how you can create a new log target class and, of course, may helpful to see how you can create a new log target class and, of course, may
also be used without any change. There are: also be used without any change. There are:
\begin{itemize}\itemsep=0pt \begin{itemize}\itemsep=0pt
\item{\bf wxLogStderr} This class logs messages to a {\it FILE *}, using \item{\bf wxLogStderr} This class logs messages to a {\it FILE *}, using
stderr by default as its name suggests. stderr by default as its name suggests.
\item{\bf wxLogStream} This class has the same functionality as wxLogStderr, \item{\bf wxLogStream} This class has the same functionality as wxLogStderr,
but uses {\it ostream} and cerr instead of {\it FILE *} and stderr. but uses {\it ostream} and cerr instead of {\it FILE *} and stderr.
\item{\bf wxLogGui} This is the standard log target for wxWindows \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's used by default if you don't do anything) and provides the
most reasonable handling of all types of messages for given platform. most reasonable handling of all types of messages for given platform.
\item{\bf wxLogWindow} This log target provides a "log console" which \item{\bf wxLogWindow} This log target provides a "log console" which
collects all messages generated by the application and also passes them to the collects all messages generated by the application and also passes them to the
previous active log target. The log window frame has a menu allowing user to previous active log target. The log window frame has a menu allowing user to
clear the log, close it completely or save all messages to file. clear the log, close it completely or save all messages to file.
\item{\bf wxLogNull} The last log class is quite particular: it doesn't do \item{\bf wxLogNull} The last log class is quite particular: it doesn't do
anything. The objects of this class may be instantiated to (temporarily) anything. The objects of this class may be instantiated to (temporarily)
suppress output of {\it wxLogXXX()} functions. As an example, trying to open a suppress output of {\it wxLogXXX()} functions. As an example, trying to open a
non-existing file will usually provoke an error message, but if you for some non-existing file will usually provoke an error message, but if you for some
reason it's unwanted, just use this construction: reason it's unwanted, just use this construction:
{\small
\begin{verbatim} \begin{verbatim}
wxFile file; wxFile file;
@@ -154,5 +142,6 @@ reason it's unwanted, just use this construction:
wxLogMessage("..."); // ok wxLogMessage("..."); // ok
\end{verbatim} \end{verbatim}
}
\end{itemize} \end{itemize}

2
docs/latex/wx/topics.tex
View File

@@ -6,7 +6,7 @@ This chapter contains a selection of topic overviews.
\input tapp.tex \input tapp.tex
\input tlog.tex \input tlog.tex
\input tconfig.tex %\input tconfig.tex
\input tbitmap.tex \input tbitmap.tex
\input tdialog.tex \input tdialog.tex
\input tfont.tex \input tfont.tex