wx.SL_INVERSE works for the big 3 now.

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

diff --git a/docs/latex/wx/tguide.tex b/docs/latex/wx/tguide.tex
index 383dd1da0b81cd431c331fcf21f863101a6bd3a4..c78f52a3454e34c2dc4c02a70371e4b6e9064009 100644 (file)
--- a/docs/latex/wx/tguide.tex
+++ b/docs/latex/wx/tguide.tex
@@ -1,6 +1,6 @@
-\section{Writing a wxWindows application: a rough guide}\label{roughguide}
+\section{Writing a wxWidgets application: a rough guide}\label{roughguide}

 
 

-To set a wxWindows application going, you will need to derive a \helpref{wxApp}{wxapp} class and
+To set a wxWidgets application going, you will need to derive a \helpref{wxApp}{wxapp} class and

 override \helpref{wxApp::OnInit}{wxapponinit}.
 
 An application must have a top-level \helpref{wxFrame}{wxframe} or \helpref{wxDialog}{wxdialog} window.
 override \helpref{wxApp::OnInit}{wxapponinit}.
 
 An application must have a top-level \helpref{wxFrame}{wxframe} or \helpref{wxDialog}{wxdialog} window.


@@ -34,15 +34,15 @@ brushes (\helpref{wxBrush}{wxbrush}) and pens (\helpref{wxPen}{wxpen}).
 To intercept events, you add a DECLARE\_EVENT\_TABLE macro to the window class declaration,
 and put a BEGIN\_EVENT\_TABLE ... END\_EVENT\_TABLE block in the implementation file. Between these
 macros, you add event macros which map the event (such as a mouse click) to a member function.
 To intercept events, you add a DECLARE\_EVENT\_TABLE macro to the window class declaration,
 and put a BEGIN\_EVENT\_TABLE ... END\_EVENT\_TABLE block in the implementation file. Between these
 macros, you add event macros which map the event (such as a mouse click) to a member function.

-These might override predefined event handlers such as \helpref{wxWindow::OnChar}{wxwindowonchar} and
-\rtfsp\helpref{wxWindow::OnMouseEvent}{wxwindowonmouseevent}.
+These might override predefined event handlers such as for \helpref{wxKeyEvent}{wxkeyevent} and
+\rtfsp\helpref{wxMouseEvent}{wxmouseevent}.

 
 Most modern applications will have an on-line, hypertext help system; for this, you
 need wxHelp and the \helpref{wxHelpController}{wxhelpcontroller} class to control
 wxHelp.
 
 GUI applications aren't all graphical wizardry. List and hash table needs are
 
 Most modern applications will have an on-line, hypertext help system; for this, you
 need wxHelp and the \helpref{wxHelpController}{wxhelpcontroller} class to control
 wxHelp.
 
 GUI applications aren't all graphical wizardry. List and hash table needs are

-catered for by \helpref{wxList}{wxlist}, \helpref{wxStringList}{wxstringlist} and \helpref{wxHashMap}{wxhashmap}.
+catered for by \helpref{wxList}{wxlist} and \helpref{wxHashMap}{wxhashmap}.

 You will undoubtedly need some platform-independent \helpref{file functions}{filefunctions},
 and you may find it handy to maintain and search a list of paths using \helpref{wxPathList}{wxpathlist}.
 There's a \helpref{miscellany}{miscellany} of operating system and other functions.
 You will undoubtedly need some platform-independent \helpref{file functions}{filefunctions},
 and you may find it handy to maintain and search a list of paths using \helpref{wxPathList}{wxpathlist}.
 There's a \helpref{miscellany}{miscellany} of operating system and other functions.