X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/eaaa6a06a25774c18d10bb8182cc1934ed0ed9aa..a8cb1d29e7fe349142d8d6be9fc9afe986340611:/docs/latex/wx/mdi.tex diff --git a/docs/latex/wx/mdi.tex b/docs/latex/wx/mdi.tex index 11666e82c5..64d7d75eb9 100644 --- a/docs/latex/wx/mdi.tex +++ b/docs/latex/wx/mdi.tex @@ -10,6 +10,10 @@ which is itself a child of \helpref{wxMDIParentFrame}{wxmdiparentframe}. \helpref{wxEvtHandler}{wxevthandler}\\ \helpref{wxObject}{wxobject} +\wxheading{Include files} + + + \wxheading{Window styles} \twocolwidtha{5cm} @@ -153,6 +157,10 @@ more \helpref{wxMDIChildFrame}{wxmdichildframe} objects. \helpref{wxEvtHandler}{wxevthandler}\\ \helpref{wxObject}{wxobject} +\wxheading{Include files} + + + \wxheading{Remarks} The client window is the area where MDI child windows exist. It doesn't have to cover the whole @@ -225,6 +233,10 @@ and is used in many popular Windows applications, such as Microsoft Word(TM). \helpref{wxEvtHandler}{wxevthandler}\\ \helpref{wxObject}{wxobject} +\wxheading{Include files} + + + \wxheading{Remarks} There may be multiple MDI parent frames in a single application, but this probably only makes sense @@ -422,6 +434,10 @@ automatically by the client window. \helpref{wxWindow}{wxwindowonsize},\rtfsp \helpref{wxMDIClientWindow}{wxmdiclientwindow} + +\pythonnote{The wxPython version of this method takes no arguments and +returns a tuple containing width and height.} + \membersection{wxMDIParentFrame::GetActiveChild}\label{wxmdiparentframegetactivechild} \constfunc{wxMDIChildFrame*}{GetActiveChild}{\void}