fixed bug in mouse handling

[wxWidgets.git] / docs / latex / wx / body.tex

diff --git a/docs/latex/wx/body.tex b/docs/latex/wx/body.tex
index e19128f347e61867b8d78fdf5f9cc6f6f9a33f78..f78cce22cee08dfed64019ea1c47a09b15d62cbc 100644 (file)
--- a/docs/latex/wx/body.tex
+++ b/docs/latex/wx/body.tex
@@ -86,7 +86,7 @@ in Windows Help, HTML and Word RTF formats.
 \item Simple-to-use, object-oriented API.
 \item Flexible event system.
 \item Graphics calls include lines, rounded rectangles, splines, polylines, etc.
 \item Simple-to-use, object-oriented API.
 \item Flexible event system.
 \item Graphics calls include lines, rounded rectangles, splines, polylines, etc.

-\item Constraint-based and sizer-based layouting.
+\item Constraint-based and sizer-based layouts.

 \item Print/preview and document/view architectures.
 \item Toolbar, notebook, tree control, advanced list control classes.
 \item PostScript generation under Unix, normal MS Windows printing on the PC.
 \item Print/preview and document/view architectures.
 \item Toolbar, notebook, tree control, advanced list control classes.
 \item PostScript generation under Unix, normal MS Windows printing on the PC.


@@ -99,7 +99,7 @@ them to the clipboard.
 \item Ready-to-use HTML window (supporting a subset of HTML).
 \item Dialog Editor for building dialogs.
 \item Network support via a family of socket and protocol classes.
 \item Ready-to-use HTML window (supporting a subset of HTML).
 \item Dialog Editor for building dialogs.
 \item Network support via a family of socket and protocol classes.

-\item Support for platform independent image procesing.
+\item Support for platform independent image processing.

 \item Built-in support for many file formats (BMP, PNG, JPEG, GIF, XPM, PNM, PCX).
 \end{itemize}
 
 \item Built-in support for many file formats (BMP, PNG, JPEG, GIF, XPM, PNM, PCX).
 \end{itemize}
 


@@ -123,7 +123,7 @@ Additions and changes:
 
 \begin{itemize}\itemsep=0pt
 \item class hierarchy changed, and restrictions about subwindow nesting lifted;
 
 \begin{itemize}\itemsep=0pt
 \item class hierarchy changed, and restrictions about subwindow nesting lifted;

-\item header files reorganised to conform to normal C++ standards;
+\item header files reorganized to conform to normal C++ standards;

 \item classes less dependent on each another, to reduce executable size;
 \item wxString used instead of char* wherever possible;
 \item the number of separate but mandatory utilities reduced;
 \item classes less dependent on each another, to reduce executable size;
 \item wxString used instead of char* wherever possible;
 \item the number of separate but mandatory utilities reduced;


@@ -190,7 +190,7 @@ Additions and changes:
 \item Many optical improvements to GTK port.
 \item Support for menu accelerators in GTK port.
 \item Enhanced and improved support for scrolling, including child windows.
 \item Many optical improvements to GTK port.
 \item Support for menu accelerators in GTK port.
 \item Enhanced and improved support for scrolling, including child windows.

-\item Complete rewrite of clipboard and drag'n'drop classes.
+\item Complete rewrite of clipboard and drag and drop classes.

 \item Improved support for ODBC databases.
 \item Improved tab traversal in dialogs.
 \end{itemize}
 \item Improved support for ODBC databases.
 \item Improved tab traversal in dialogs.
 \end{itemize}


@@ -449,7 +449,7 @@ fine on some platforms, and then fail under Windows.
 \section{Architecture dependency}
 
 A problem which sometimes arises from writing multi-platform programs is that
 \section{Architecture dependency}
 
 A problem which sometimes arises from writing multi-platform programs is that

-the basic C types are not defiend the same on all platforms. This holds true
+the basic C types are not defined the same on all platforms. This holds true

 for both the length in bits of the standard types (such as int and long) as 
 well as their byte order, which might be little endian (typically
 on Intel computers) or big endian (typically on some Unix workstations). wxWindows
 for both the length in bits of the standard types (such as int and long) as 
 well as their byte order, which might be little endian (typically
 on Intel computers) or big endian (typically on some Unix workstations). wxWindows


@@ -492,7 +492,7 @@ its own run-time type information system, implemented using macros.
 
 Some compilers (e.g. the native IRIX cc) define NULL to be 0L so that
 no conversion to pointers is allowed. Because of that, all these
 
 Some compilers (e.g. the native IRIX cc) define NULL to be 0L so that
 no conversion to pointers is allowed. Because of that, all these

-occurences of NULL in the GTK port use an explicit conversion such 
+occurrences of NULL in the GTK port use an explicit conversion such 

 as
 
 {\small
 as
 
 {\small


@@ -527,7 +527,7 @@ X and Windows parts of the library) conditional
 compilation that under Unix, includes a minimal set of headers;
 and when using Visual C++, includes {\tt wx.h}. This should help provide
 the optimal compilation for each compiler, although it is
 compilation that under Unix, includes a minimal set of headers;
 and when using Visual C++, includes {\tt wx.h}. This should help provide
 the optimal compilation for each compiler, although it is

-biassed towards the precompiled headers facility available
+biased towards the precompiled headers facility available

 in Microsoft C++.
 
 \section{File handling}
 in Microsoft C++.
 
 \section{File handling}


@@ -577,7 +577,7 @@ more easily accessed via the Contributions page on the Web site.
 wxHelp is a stand-alone program, written using wxWindows,
 for displaying hypertext help. It is necessary since not all target
 systems (notably X) supply an adequate
 wxHelp is a stand-alone program, written using wxWindows,
 for displaying hypertext help. It is necessary since not all target
 systems (notably X) supply an adequate

-standard for on-line help. wxHelp is modelled on the MS Windows help
+standard for on-line help. wxHelp is modeled on the MS Windows help

 system, with contents, search and browse buttons, but does not reformat
 text to suit the size of window, as WinHelp does, and its input files
 are uncompressed ASCII with some embedded font commands and an .xlp
 system, with contents, search and browse buttons, but does not reformat
 text to suit the size of window, as WinHelp does, and its input files
 are uncompressed ASCII with some embedded font commands and an .xlp


@@ -690,9 +690,9 @@ it can alert you to problems later on.
 \subsection{Use wxString in preference to character arrays}
 
 Using wxString can be much safer and more convenient than using char *.
 \subsection{Use wxString in preference to character arrays}
 
 Using wxString can be much safer and more convenient than using char *.

-Again, I haven't practised what I'm preaching, but I'm now trying to use
+Again, I haven't practiced what I'm preaching, but I'm now trying to use

 wxString wherever possible. You can reduce the possibility of memory
 wxString wherever possible. You can reduce the possibility of memory

-leaks substantially, and it's much more convenient to use the overloaded
+leaks substantially, and it is much more convenient to use the overloaded

 operators than functions such as strcmp. wxString won't add a significant
 overhead to your program; the overhead is compensated for by easier
 manipulation (which means less code).
 operators than functions such as strcmp. wxString won't add a significant
 overhead to your program; the overhead is compensated for by easier
 manipulation (which means less code).


@@ -721,7 +721,7 @@ kinds of bitmap depending on platform (see the section on resource files).
 
 \subsection{Positive thinking}
 
 
 \subsection{Positive thinking}
 

-It's common to blow up the problem in one's imagination, so that it seems to threaten
+It is common to blow up the problem in one's imagination, so that it seems to threaten

 weeks, months or even years of work. The problem you face may seem insurmountable:
 but almost never is. Once you have been programming for some time, you will be able
 to remember similar incidents that threw you into the depths of despair. But
 weeks, months or even years of work. The problem you face may seem insurmountable:
 but almost never is. Once you have been programming for some time, you will be able
 to remember similar incidents that threw you into the depths of despair. But


@@ -748,8 +748,8 @@ deallocation, this can still give totally spurious results!
 
 \subsection{Use a debugger}
 
 
 \subsection{Use a debugger}
 

-This sounds like facetious advice, but it's surprising how often people
-don't use a debugger. Often it's an overhead to install or learn how to
+This sounds like facetious advice, but it is surprising how often people
+don't use a debugger. Often it is an overhead to install or learn how to

 use a debugger, but it really is essential for anything but the most
 trivial programs.
 
 use a debugger, but it really is essential for anything but the most
 trivial programs.
 


@@ -778,13 +778,13 @@ 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 
+Under Windows, it is worth running your program with 

 \urlref{DbgView}{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
-possible it'll show invalid handles being used. You may have fun seeing
+some other program that shows Windows-generated debug messages. It is
+possible it will show invalid handles being used. You may have fun seeing

 what commercial programs cause these normally hidden errors! Microsoft
 recommend using the debugging version of Windows, which shows up even
 what commercial programs cause these normally hidden errors! Microsoft
 recommend using the debugging version of Windows, which shows up even

-more problems. However, I doubt it's worth the hassle for most
+more problems. However, I doubt it is worth the hassle for most

 applications. wxWindows is designed to minimize the possibility of such
 errors, but they can still happen occasionally, slipping through unnoticed
 because they are not severe enough to cause a crash.
 applications. wxWindows is designed to minimize the possibility of such
 errors, but they can still happen occasionally, slipping through unnoticed
 because they are not severe enough to cause a crash.