X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/f9b1708cf57d57bc91f4e870a4646efd1f174c3d..93bfe54527a7a64ea87cdc03be3015f7963fd227:/docs/latex/wx/layalgor.tex

diff --git a/docs/latex/wx/layalgor.tex b/docs/latex/wx/layalgor.tex
index 6b0ff45c75..fb39325e37 100644
--- 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
@@ -58,6 +58,10 @@ way of specifying layouts for which the normal constraint system is unsuitable.
 
 \helpref{wxObject}{wxobject}
 
+\wxheading{Include files}
+
+<wx/laywin.h>
+
 \wxheading{Event handling}
 
 The algorithm object does not respond to events, but itself generates the
@@ -102,13 +106,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}
 
@@ -137,5 +141,8 @@ The MDI client window is set to occupy the remaining space.
 
 Lays out the children of a normal frame or other window.
 
-{\it mainWindow} is set to occupy the remaining space.
+{\it mainWindow} is set to occupy the remaining space. If this is not specified, then
+the last window that responds to a calculate layout event in query mode will get the remaining space
+(that is, a non-query OnCalculateLayout event will not be sent to this window and the window will be set
+to the remaining size).