1 \section{\class{wxMDIChildFrame
}}\label{wxmdichildframe
}
3 An MDI child frame is a frame that can only exist on a
\helpref{wxMDIClientWindow
}{wxmdiclientwindow
},
4 which is itself a child of
\helpref{wxMDIParentFrame
}{wxmdiparentframe
}.
6 \wxheading{Derived from
}
8 \helpref{wxFrame
}{wxframe
}\\
9 \helpref{wxWindow
}{wxwindow
}\\
10 \helpref{wxEvtHandler
}{wxevthandler
}\\
11 \helpref{wxObject
}{wxobject
}
13 \wxheading{Include files
}
17 \wxheading{Window styles
}
20 \begin{twocollist
}\itemsep=
0pt
21 \twocolitem{\windowstyle{wxCAPTION
}}{Puts a caption on the frame.
}
22 \twocolitem{\windowstyle{wxDEFAULT
\_FRAME\_STYLE}}{Defined as
{\bf wxMINIMIZE
\_BOX \pipe wxMAXIMIZE
\_BOX \pipe wxTHICK
\_FRAME \pipe wxSYSTEM
\_MENU \pipe wxCAPTION
}.
}
23 \twocolitem{\windowstyle{wxICONIZE
}}{Display the frame iconized (minimized) (Windows only).
}
24 \twocolitem{\windowstyle{wxMAXIMIZE
}}{Displays the frame maximized (Windows only).
}
25 \twocolitem{\windowstyle{wxMAXIMIZE
\_BOX}}{Displays a maximize box on the frame (Windows and Motif only).
}
26 \twocolitem{\windowstyle{wxMINIMIZE
}}{Identical to
{\bf wxICONIZE
}.
}
27 \twocolitem{\windowstyle{wxMINIMIZE
\_BOX}}{Displays a minimize box on the frame (Windows and Motif only).
}
28 \twocolitem{\windowstyle{wxRESIZE
\_BORDER}}{Displays a resizeable border around the window (Motif only;
29 for Windows, it is implicit in wxTHICK
\_FRAME).
}
30 \twocolitem{\windowstyle{wxSTAY
\_ON\_TOP}}{Stay on top of other windows (Windows only).
}
31 \twocolitem{\windowstyle{wxSYSTEM
\_MENU}}{Displays a system menu (Windows and Motif only).
}
32 \twocolitem{\windowstyle{wxTHICK
\_FRAME}}{Displays a thick frame around the window (Windows and Motif only).
}
35 See also
\helpref{window styles overview
}{windowstyles
}.
39 Although internally an MDI child frame is a child of the MDI client window, in wxWidgets
40 you create it as a child of
\helpref{wxMDIParentFrame
}{wxmdiparentframe
}. You can usually
41 forget that the client window exists.
43 MDI child frames are clipped to the area of the MDI client window, and may be iconized
46 You can associate a menubar with a child frame as usual, although an MDI child doesn't display
47 its menubar under its own title bar. The MDI parent frame's menubar will be changed to
48 reflect the currently active child frame. If there are currently no children, the parent
49 frame's own menubar will be displayed.
53 \helpref{wxMDIClientWindow
}{wxmdiclientwindow
},
\helpref{wxMDIParentFrame
}{wxmdiparentframe
},
\rtfsp
54 \helpref{wxFrame
}{wxframe
}
56 \latexignore{\rtfignore{\wxheading{Members
}}}
58 \membersection{wxMDIChildFrame::wxMDIChildFrame
}\label{wxmdichildframector
}
60 \func{}{wxMDIChildFrame
}{\void}
64 \func{}{wxMDIChildFrame
}{\param{wxMDIParentFrame*
}{parent
},
\param{wxWindowID
}{id
},
\rtfsp
65 \param{const wxString\&
}{title
},
\param{const wxPoint\&
}{ pos = wxDefaultPosition
},
\rtfsp
66 \param{const wxSize\&
}{ size = wxDefaultSize
},
\param{long
}{ style = wxDEFAULT
\_FRAME\_STYLE},
\rtfsp
67 \param{const wxString\&
}{name = ``frame"
}}
69 Constructor, creating the window.
71 \wxheading{Parameters
}
73 \docparam{parent
}{The window parent. This should not be NULL.
}
75 \docparam{id
}{The window identifier. It may take a value of -
1 to indicate a default value.
}
77 \docparam{title
}{The caption to be displayed on the frame's title bar.
}
79 \docparam{pos
}{The window position. A value of (-
1, -
1) indicates a default position, chosen by
80 either the windowing system or wxWidgets, depending on platform.
}
82 \docparam{size
}{The window size. A value of (-
1, -
1) indicates a default size, chosen by
83 either the windowing system or wxWidgets, depending on platform.
}
85 \docparam{style
}{The window style. See
\helpref{wxMDIChildFrame
}{wxmdichildframe
}.
}
87 \docparam{name
}{The name of the window. This parameter is used to associate a name with the item,
88 allowing the application user to set Motif resource values for
97 \helpref{wxMDIChildFrame::Create
}{wxmdichildframecreate
}
99 \membersection{wxMDIChildFrame::
\destruct{wxMDIChildFrame
}}\label{wxmdichildframedtor
}
101 \func{}{\destruct{wxMDIChildFrame
}}{\void}
103 Destructor. Destroys all child windows and menu bar if present.
105 \membersection{wxMDIChildFrame::Activate
}\label{wxmdichildframeactivate
}
107 \func{void
}{Activate
}{\void}
109 Activates this MDI child frame.
113 \helpref{wxMDIChildFrame::Maximize
}{wxmdichildframemaximize
},
\rtfsp
114 \helpref{wxMDIChildFrame::Restore
}{wxmdichildframerestore
}
116 \membersection{wxMDIChildFrame::Create
}\label{wxmdichildframecreate
}
118 \func{bool
}{Create
}{\param{wxWindow*
}{parent
},
\param{wxWindowID
}{id
},
\rtfsp
119 \param{const wxString\&
}{title
},
\param{const wxPoint\&
}{ pos = wxDefaultPosition
},
\rtfsp
120 \param{const wxSize\&
}{ size = wxDefaultSize
},
\param{long
}{ style = wxDEFAULT
\_FRAME\_STYLE},
\rtfsp
121 \param{const wxString\&
}{name = ``frame"
}}
123 Used in two-step frame construction. See
\helpref{wxMDIChildFrame::wxMDIChildFrame
}{wxmdichildframector
}\rtfsp
126 \membersection{wxMDIChildFrame::Maximize
}\label{wxmdichildframemaximize
}
128 \func{void
}{Maximize
}{\void}
130 Maximizes this MDI child frame.
134 \helpref{wxMDIChildFrame::Activate
}{wxmdichildframeactivate
},
\rtfsp
135 \helpref{wxMDIChildFrame::Restore
}{wxmdichildframerestore
}
137 \membersection{wxMDIChildFrame::Restore
}\label{wxmdichildframerestore
}
139 \func{void
}{Restore
}{\void}
141 Restores this MDI child frame (unmaximizes).
145 \helpref{wxMDIChildFrame::Activate
}{wxmdichildframeactivate
},
\rtfsp
146 \helpref{wxMDIChildFrame::Maximize
}{wxmdichildframemaximize
}
148 \section{\class{wxMDIClientWindow
}}\label{wxmdiclientwindow
}
150 An MDI client window is a child of
\helpref{wxMDIParentFrame
}{wxmdiparentframe
}, and manages zero or
151 more
\helpref{wxMDIChildFrame
}{wxmdichildframe
} objects.
153 \wxheading{Derived from
}
155 \helpref{wxWindow
}{wxwindow
}\\
156 \helpref{wxEvtHandler
}{wxevthandler
}\\
157 \helpref{wxObject
}{wxobject
}
159 \wxheading{Include files
}
165 The client window is the area where MDI child windows exist. It doesn't have to cover the whole
166 parent frame; other windows such as toolbars and a help window might coexist with it.
167 There can be scrollbars on a client window, which are controlled by the parent window style.
169 The
{\bf wxMDIClientWindow
} class is usually adequate without further derivation, and it is created
170 automatically when the MDI parent frame is created. If the application needs to derive a new class,
171 the function
\helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
} must be
172 overridden in order to give an opportunity to use a different class of client window.
174 Under Windows
95, the client window will automatically have a sunken border style when
175 the active child is not maximized, and no border style when a child is maximized.
179 \helpref{wxMDIChildFrame
}{wxmdichildframe
},
\helpref{wxMDIParentFrame
}{wxmdiparentframe
},
\rtfsp
180 \helpref{wxFrame
}{wxframe
}
182 \latexignore{\rtfignore{\wxheading{Members
}}}
184 \membersection{wxMDIClientWindow::wxMDIClientWindow
}\label{wxmdiclientwindowctor
}
186 \func{}{wxMDIClientWindow
}{\void}
190 \func{}{wxMDIClientWindow
}{\param{wxMDIParentFrame*
}{parent
},
\param{long
}{ style =
0}}
192 Constructor, creating the window.
194 \wxheading{Parameters
}
196 \docparam{parent
}{The window parent.
}
198 \docparam{style
}{The window style. Currently unused.
}
202 The second style of constructor is called within
\helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
}.
206 \helpref{wxMDIParentFrame::wxMDIParentFrame
}{wxmdiparentframector
},
\rtfsp
207 \helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
}
209 \membersection{wxMDIClientWindow::
\destruct{wxMDIClientWindow
}}\label{wxmdiclientwindowdtor
}
211 \func{}{\destruct{wxMDIClientWindow
}}{\void}
215 \membersection{wxMDIClientWindow::CreateClient
}\label{wxmdiclientwindowcreateclient
}
217 \func{bool
}{CreateClient
}{\param{wxMDIParentFrame*
}{parent
},
\param{long
}{ style =
0}}
219 Used in two-step frame construction. See
\helpref{wxMDIClientWindow::wxMDIClientWindow
}{wxmdiclientwindowctor
}\rtfsp
222 \section{\class{wxMDIParentFrame
}}\label{wxmdiparentframe
}
224 An MDI (Multiple Document Interface) parent frame is a window which can contain
225 MDI child frames in its own `desktop'. It is a convenient way to avoid window clutter,
226 and is used in many popular Windows applications, such as Microsoft Word(TM).
228 \wxheading{Derived from
}
230 \helpref{wxFrame
}{wxframe
}\\
231 \helpref{wxWindow
}{wxwindow
}\\
232 \helpref{wxEvtHandler
}{wxevthandler
}\\
233 \helpref{wxObject
}{wxobject
}
235 \wxheading{Include files
}
241 There may be multiple MDI parent frames in a single application, but this probably only makes sense
242 within programming development environments.
244 Child frames may be of class
\helpref{wxMDIChildFrame
}{wxmdichildframe
} (contained
245 within the parent frame) or
\helpref{wxFrame
}{wxframe
} (shown as a top-level frame).
247 An MDI parent frame always has a
\helpref{wxMDIClientWindow
}{wxmdiclientwindow
} associated with it, which
248 is the parent for MDI client frames.
249 This client window may be resized to accommodate non-MDI windows, as seen in Microsoft Visual C++ (TM) and
250 Microsoft Publisher (TM), where a documentation window is placed to one side of the workspace.
252 MDI remains popular despite dire warnings from Microsoft itself that MDI is an obsolete
253 user interface style.
255 The implementation is native in Windows, and simulated under Motif. Under Motif,
256 the child window frames will often have a different appearance from other frames
257 because the window decorations are simulated.
259 \wxheading{Window styles
}
262 \begin{twocollist
}\itemsep=
0pt
263 \twocolitem{\windowstyle{wxCAPTION
}}{Puts a caption on the frame.
}
264 \twocolitem{\windowstyle{wxDEFAULT
\_FRAME\_STYLE}}{Defined as
{\bf wxMINIMIZE
\_BOX \pipe wxMAXIMIZE
\_BOX \pipe wxTHICK
\_FRAME \pipe wxSYSTEM
\_MENU \pipe wxCAPTION
}.
}
265 \twocolitem{\windowstyle{wxHSCROLL
}}{Displays a horizontal scrollbar in the
{\it client window
}, allowing
266 the user to view child frames that are off the current view.
}
267 \twocolitem{\windowstyle{wxICONIZE
}}{Display the frame iconized (minimized) (Windows only).
}
268 \twocolitem{\windowstyle{wxMAXIMIZE
}}{Displays the frame maximized (Windows only).
}
269 \twocolitem{\windowstyle{wxMAXIMIZE
\_BOX}}{Displays a maximize box on the frame (Windows and Motif only).
}
270 \twocolitem{\windowstyle{wxMINIMIZE
}}{Identical to
{\bf wxICONIZE
}.
}
271 \twocolitem{\windowstyle{wxMINIMIZE
\_BOX}}{Displays a minimize box on the frame (Windows and Motif only).
}
272 \twocolitem{\windowstyle{wxRESIZE
\_BORDER}}{Displays a resizeable border around the window (Motif only;
273 for Windows, it is implicit in wxTHICK
\_FRAME).
}
274 \twocolitem{\windowstyle{wxSTAY
\_ON\_TOP}}{Stay on top of other windows (Windows only).
}
275 \twocolitem{\windowstyle{wxSYSTEM
\_MENU}}{Displays a system menu (Windows and Motif only).
}
276 \twocolitem{\windowstyle{wxTHICK
\_FRAME}}{Displays a thick frame around the window (Windows and Motif only).
}
277 \twocolitem{\windowstyle{wxVSCROLL
}}{Displays a vertical scrollbar in the
{\it client window
}, allowing
278 the user to view child frames that are off the current view.
}
279 \twocolitem{\windowstyle{wxFRAME
\_NO\_WINDOW\_MENU}}{Under Windows, removes the Window menu that is normally
280 added automatically.
}
283 See also
\helpref{window styles overview
}{windowstyles
}.
287 \helpref{wxMDIChildFrame
}{wxmdichildframe
},
\helpref{wxMDIClientWindow
}{wxmdiclientwindow
},
\rtfsp
288 \helpref{wxFrame
}{wxframe
},
\helpref{wxDialog
}{wxdialog
}
290 \latexignore{\rtfignore{\wxheading{Members
}}}
292 \membersection{wxMDIParentFrame::wxMDIParentFrame
}\label{wxmdiparentframector
}
294 \func{}{wxMDIParentFrame
}{\void}
298 \func{}{wxMDIParentFrame
}{\param{wxWindow*
}{parent
},
\param{wxWindowID
}{id
},
\rtfsp
299 \param{const wxString\&
}{title
},
\param{const wxPoint\&
}{ pos = wxDefaultPosition
},
\rtfsp
300 \param{const wxSize\&
}{ size = wxDefaultSize
},
\param{long
}{ style = wxDEFAULT
\_FRAME\_STYLE \pipe wxVSCROLL
\pipe wxHSCROLL
},
\rtfsp
301 \param{const wxString\&
}{name = ``frame"
}}
303 Constructor, creating the window.
305 \wxheading{Parameters
}
307 \docparam{parent
}{The window parent. This should be NULL.
}
309 \docparam{id
}{The window identifier. It may take a value of -
1 to indicate a default value.
}
311 \docparam{title
}{The caption to be displayed on the frame's title bar.
}
313 \docparam{pos
}{The window position. A value of (-
1, -
1) indicates a default position, chosen by
314 either the windowing system or wxWidgets, depending on platform.
}
316 \docparam{size
}{The window size. A value of (-
1, -
1) indicates a default size, chosen by
317 either the windowing system or wxWidgets, depending on platform.
}
319 \docparam{style
}{The window style. See
\helpref{wxMDIParentFrame
}{wxmdiparentframe
}.
}
321 \docparam{name
}{The name of the window. This parameter is used to associate a name with the item,
322 allowing the application user to set Motif resource values for
327 During the construction of the frame, the client window will be created. To use a different class
328 from
\helpref{wxMDIClientWindow
}{wxmdiclientwindow
}, override
\rtfsp
329 \helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
}.
331 Under Windows
95, the client window will automatically have a sunken border style when
332 the active child is not maximized, and no border style when a child is maximized.
336 \helpref{wxMDIParentFrame::Create
}{wxmdiparentframecreate
},
\rtfsp
337 \helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
}
339 \membersection{wxMDIParentFrame::
\destruct{wxMDIParentFrame
}}\label{wxmdiparentframedtor
}
341 \func{}{\destruct{wxMDIParentFrame
}}{\void}
343 Destructor. Destroys all child windows and menu bar if present.
345 \membersection{wxMDIParentFrame::ActivateNext
}\label{wxmdiparentframeactivatenext
}
347 \func{void
}{ActivateNext
}{\void}
349 Activates the MDI child following the currently active one.
353 \helpref{wxMDIParentFrame::ActivatePrevious
}{wxmdiparentframeactivateprevious
}
355 \membersection{wxMDIParentFrame::ActivatePrevious
}\label{wxmdiparentframeactivateprevious
}
357 \func{void
}{ActivatePrevious
}{\void}
359 Activates the MDI child preceding the currently active one.
363 \helpref{wxMDIParentFrame::ActivateNext
}{wxmdiparentframeactivatenext
}
366 \membersection{wxMDIParentFrame::ArrangeIcons
}\label{wxmdiparentframearrangeicons
}
368 \func{void
}{ArrangeIcons
}{\void}
370 Arranges any iconized (minimized) MDI child windows.
374 \helpref{wxMDIParentFrame::Cascade
}{wxmdiparentframecascade
},
\rtfsp
375 \helpref{wxMDIParentFrame::Tile
}{wxmdiparentframetile
}
377 \membersection{wxMDIParentFrame::Cascade
}\label{wxmdiparentframecascade
}
379 \func{void
}{Cascade
}{\void}
381 Arranges the MDI child windows in a cascade.
385 \helpref{wxMDIParentFrame::Tile
}{wxmdiparentframetile
},
\rtfsp
386 \helpref{wxMDIParentFrame::ArrangeIcons
}{wxmdiparentframearrangeicons
}
388 \membersection{wxMDIParentFrame::Create
}\label{wxmdiparentframecreate
}
390 \func{bool
}{Create
}{\param{wxWindow*
}{parent
},
\param{wxWindowID
}{id
},
\rtfsp
391 \param{const wxString\&
}{title
},
\param{const wxPoint\&
}{ pos = wxDefaultPosition
},
\rtfsp
392 \param{const wxSize\&
}{ size = wxDefaultSize
},
\param{long
}{ style = wxDEFAULT
\_FRAME\_STYLE \pipe wxVSCROLL
\pipe wxHSCROLL
},
\rtfsp
393 \param{const wxString\&
}{name = ``frame"
}}
395 Used in two-step frame construction. See
\helpref{wxMDIParentFrame::wxMDIParentFrame
}{wxmdiparentframector
}\rtfsp
398 \membersection{wxMDIParentFrame::GetClientSize
}\label{wxmdiparentframegetclientsize
}
400 \constfunc{virtual void
}{GetClientSize
}{\param{int*
}{width
},
\param{int*
}{height
}}
402 This gets the size of the frame `client area' in pixels.
404 \wxheading{Parameters
}
406 \docparam{width
}{Receives the client width in pixels.
}
408 \docparam{height
}{Receives the client height in pixels.
}
412 The client area is the area which may be drawn on by the programmer, excluding title bar, border, status bar,
413 and toolbar if present.
415 If you wish to manage your own toolbar (or perhaps you have more than one),
416 provide an
{\bf OnSize
} event handler. Call
{\bf GetClientSize
} to
417 find how much space there is for your windows and don't forget to set the size and position
418 of the MDI client window as well as your toolbar and other windows (but not the status bar).
420 If you have set a toolbar with
\helpref{wxMDIParentFrame::SetToolbar
}{wxmdiparentframesettoolbar
},
421 the client size returned will have subtracted the toolbar height. However, the available positions
422 for the client window and other windows of the frame do not start at zero - you must add the toolbar height.
424 The position and size of the status bar and toolbar (if known to the frame) are always managed
425 by
{\bf wxMDIParentFrame
}, regardless of what behaviour is defined in your
{\bf OnSize
} event handler.
426 However, the client window position and size are always set in
{\bf OnSize
}, so if you override this
427 event handler, make sure you deal with the client window.
429 You do not have to manage the size and position of MDI child windows, since they are managed
430 automatically by the client window.
434 \helpref{wxMDIParentFrame::GetToolBar
}{wxmdiparentframegettoolbar
},
\rtfsp
435 \helpref{wxMDIParentFrame::SetToolBar
}{wxmdiparentframesettoolbar
},
\rtfsp
436 \helpref{wxMDIClientWindow
}{wxmdiclientwindow
}
439 \pythonnote{The wxPython version of this method takes no arguments and
440 returns a tuple containing width and height.
}
442 \membersection{wxMDIParentFrame::GetActiveChild
}\label{wxmdiparentframegetactivechild
}
444 \constfunc{wxMDIChildFrame*
}{GetActiveChild
}{\void}
446 Returns a pointer to the active MDI child, if there is one.
448 \membersection{wxMDIParentFrame::GetClientWindow
}\label{wxmdiparentframegetclientwindow
}
450 \constfunc{wxMDIClientWindow*
}{GetClientWindow
}{\void}
452 Returns a pointer to the client window.
456 \helpref{wxMDIParentFrame::OnCreateClient
}{wxmdiparentframeoncreateclient
}
458 \membersection{wxMDIParentFrame::GetToolBar
}\label{wxmdiparentframegettoolbar
}
460 \constfunc{virtual wxWindow*
}{GetToolBar
}{\void}
462 Returns the window being used as the toolbar for this frame.
466 \helpref{wxMDIParentFrame::SetToolBar
}{wxmdiparentframesettoolbar
}
468 \membersection{wxMDIParentFrame::GetWindowMenu
}\label{wxmdiparentframegetwindowmenu
}
470 \constfunc{wxMenu*
}{GetWindowMenu
}{\void}
472 Returns the current Window menu (added by wxWidgets to the menubar). This function
473 is available under Windows only.
475 \membersection{wxMDIParentFrame::OnCreateClient
}\label{wxmdiparentframeoncreateclient
}
477 \func{virtual wxMDIClientWindow*
}{OnCreateClient
}{\void}
479 Override this to return a different kind of client window. If you override this function,
480 you must create your parent frame in two stages, or your function will never be called,
481 due to the way C++ treats virtual functions called from constructors. For example:
484 frame = new MyParentFrame;
485 frame->Create(parent, myParentFrameId, wxT("My Parent Frame"));
490 You might wish to derive from
\helpref{wxMDIClientWindow
}{wxmdiclientwindow
} in order
491 to implement different erase behaviour, for example, such as painting a bitmap
494 Note that it is probably impossible to have a client window that scrolls as well as painting
495 a bitmap or pattern, since in
{\bf OnScroll
}, the scrollbar positions always return zero.
496 (Solutions to:
{\tt julian.smart@btopenworld.com
}).
500 \helpref{wxMDIParentFrame::GetClientWindow
}{wxmdiparentframegetclientwindow
},
\rtfsp
501 \helpref{wxMDIClientWindow
}{wxmdiclientwindow
}
503 \membersection{wxMDIParentFrame::SetToolBar
}\label{wxmdiparentframesettoolbar
}
505 \func{virtual void
}{SetToolBar
}{\param{wxWindow*
}{ toolbar
}}
507 Sets the window to be used as a toolbar for this
508 MDI parent window. It saves the application having to manage the positioning
509 of the toolbar MDI client window.
511 \wxheading{Parameters
}
513 \docparam{toolbar
}{Toolbar to manage.
}
517 When the frame is resized, the toolbar is resized to be the width of
518 the frame client area, and the toolbar height is kept the same.
520 The parent of the toolbar must be this frame.
522 If you wish to manage your own toolbar (or perhaps you have more than one),
523 don't call this function, and instead manage your subwindows and the MDI client window by
524 providing an
{\bf OnSize
} event handler. Call
\helpref{wxMDIParentFrame::GetClientSize
}{wxmdiparentframegetclientsize
} to
525 find how much space there is for your windows.
527 Note that SDI (normal) frames and MDI child windows must always have their
528 toolbars managed by the application.
532 \helpref{wxMDIParentFrame::GetToolBar
}{wxmdiparentframegettoolbar
},
\rtfsp
533 \helpref{wxMDIParentFrame::GetClientSize
}{wxmdiparentframegetclientsize
}
535 \membersection{wxMDIParentFrame::SetWindowMenu
}\label{wxmdiparentframesetwindowmenu
}
537 \func{void
}{SetWindowMenu
}{\param{wxMenu*
}{ menu
}}
539 Call this to change the current Window menu. Ownership of the menu object passes to
540 the frame when you call this function.
542 This call is available under Windows only.
544 To remove the window completely, use the wxFRAME
\_NO\_WINDOW\_MENU window style.
546 \membersection{wxMDIParentFrame::Tile
}\label{wxmdiparentframetile
}
548 \func{void
}{Tile
}{\void}
550 Tiles the MDI child windows.
554 \helpref{wxMDIParentFrame::Cascade
}{wxmdiparentframecascade
},
\rtfsp
555 \helpref{wxMDIParentFrame::ArrangeIcons
}{wxmdiparentframearrangeicons
}