X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2f82899bba49ec8c6683aeffccaba030ad95da6d..c266eff98c5e44012647f54f38a1e29ecabd8759:/docs/latex/wx/layalgor.tex?ds=sidebyside diff --git a/docs/latex/wx/layalgor.tex b/docs/latex/wx/layalgor.tex index 76a36feb10..cfbcb42af9 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 @@ -62,6 +62,10 @@ way of specifying layouts for which the normal constraint system is unsuitable. +\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}