Added wxDataViewModel::GetChildren() (removed GetSibling() and GetFirstChild())

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

diff --git a/docs/latex/wx/layalgor.tex b/docs/latex/wx/layalgor.tex
index 76a36feb10fbbff32aed2a1ac59bd783874c1832..cfbcb42af9e114a96344401b71fa8cfe060b62e3 100644 (file)
--- a/docs/latex/wx/layalgor.tex
+++ b/docs/latex/wx/layalgor.tex
@@ -40,7 +40,7 @@ bottom of the remaining client area. This scheme implies that order of window cr
 Say you wish to have an extra toolbar at the top of the frame, a project window to the left of
 the MDI client window, and an output window above the status bar. You should therefore create
 the windows in this order: toolbar, output window, project window. This ensures that the toolbar and
-output window take up space at the top and bottom, and then the remaining height inbetween is used for
+output window take up space at the top and bottom, and then the remaining height in-between is used for
 the project window.
 
 wxLayoutAlgorithm is quite independent of the way in which
@@ -62,6 +62,10 @@ way of specifying layouts for which the normal constraint system is unsuitable.
 
 <wx/laywin.h>
 
+\wxheading{Library}
+
+\helpref{wxAdv}{librarieslist}
+
 \wxheading{Event handling}
 
 The algorithm object does not respond to events, but itself generates the
@@ -106,13 +110,13 @@ enum wxLayoutAlignment {
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 
-\membersection{wxLayoutAlgorithm::wxLayoutAlgorithm}
+\membersection{wxLayoutAlgorithm::wxLayoutAlgorithm}\label{wxlayoutalgorithmctor}
 
 \func{}{wxLayoutAlgorithm}{\void}
 
 Default constructor.
 
-\membersection{wxLayoutAlgorithm::\destruct{wxLayoutAlgorithm}}
+\membersection{wxLayoutAlgorithm::\destruct{wxLayoutAlgorithm}}\label{wxlayoutalgorithmdtor}
 
 \func{}{\destruct{wxLayoutAlgorithm}}{\void}