\wxheading{Derived from}
-\helpref{wxObject}{wxobject}\\
-\helpref{wxClientDataContainer}{wxclientdatacontainer}
+\helpref{wxObject}{wxobject}
\wxheading{Include files}
<wx/sizer.h>
+\wxheading{Library}
+
+\helpref{wxCore}{librarieslist}
+
\wxheading{See also}
\helpref{Sizer overview}{sizeroverview}
\func{wxSize}{CalcMin}{\void}
This method is abstract and has to be overwritten by any derived class.
-Here, the sizer will do the actual calculation of its children minimal sizes.
+Here, the sizer will do the actual calculation of its children's minimal sizes.
\membersection{wxSizer::Clear}\label{wxsizerclear}
Returns pointer to item or NULL.
+\membersection{wxSizer::GetItemById}\label{wxsizergetitembyid}
+
+\func{wxSizerItem *}{GetItemById}{\param{int }{id}, \param{bool }{recursive = false}}
+
+Finds item of the sizer which has the given \arg{id}. This \arg{id} is not the
+window id but the id of the wxSizerItem itself. This is mainly useful for
+retrieving the sizers created from XRC resources.
+
+Use parameter \arg{recursive} to search in subsizers too.
+
+Returns pointer to item or \NULL.
+
\membersection{wxSizer::GetSize}\label{wxsizergetsize}
example, instead of
\begin{verbatim}
- sizer->Add(ctrl, 0, wxEXPAND | wxBORDER, 10);
+ sizer->Add(ctrl, 0, wxEXPAND | wxALL, 10);
\end{verbatim}
you can now write
object itself to allowing chaining multiple methods calls like in the examples
above.
+\wxheading{See also}
+
+\helpref{wxSizer}{wxsizer}
+
+\wxheading{Derived from}
+
+No base class
+
+\wxheading{Include files}
+
+<wx/sizer.h>
+
+\wxheading{Library}
+
+\helpref{wxCore}{librarieslist}
+
+\latexignore{\rtfignore{\wxheading{Members}}}
\membersection{wxSizerFlags::wxSizerFlags}\label{wxsizerflagsctor}