Navigation

Table Of Contents

Previous topic

MDIClientWindow

Next topic

MappingMode

This Page

phoenix_title MDIParentFrame

An MDI (Multiple Document Interface) parent frame is a window which can contain MDI child frames in its client area which emulates the full desktop.

MDI is a user-interface model in which all the window reside inside the single parent window as opposed to being separate from each other. It remains popular despite dire warnings from Microsoft itself (which popularized this model in the first model) that MDI is obsolete.

An MDI parent frame always has a MDIClientWindow associated with it, which is the parent for MDI child frames. In the simplest case, the client window takes up the entire parent frame area but it is also possible to resize it to be smaller in order to have other windows in the frame, a typical example is using a sidebar along one of the window edges.

The appearance of MDI applications differs between different ports. The classic MDI model, with child windows which can be independently moved, resized etc, is only available under MSW, which provides native support for it. In Mac ports, multiple top level windows are used for the MDI children too and the MDI parent frame itself is invisible, to accommodate the native look and feel requirements. In all the other ports, a tab-based MDI implementation (sometimes called TDI) is used and so at most one MDI child is visible at any moment (child frames are always maximized).

Although it is possible to have multiple MDI parent frames, a typical MDI application has a single MDI parent frame window inside which multiple MDI child frames, i.e. objects of class MDIChildFrame, can be created.

styles Window Styles

This class supports the following styles:

There are no special styles for this class, all Frame styles apply to it in the usual way. The only exception is that HSCROLL and VSCROLL styles apply not to the frame itself but to the client window, so that using them enables horizontal and vertical scrollbars for this window and not the frame.

See also

MDIChildFrame, MDIClientWindow, Frame, Dialog


class_hierarchy Inheritance Diagram

Inheritance diagram for class MDIParentFrame

Inheritance diagram of MDIParentFrame


sub_classes Known Subclasses

DocMDIParentFrame


method_summary Methods Summary

__init__ Default constructor.
ActivateNext Activates the MDI child following the currently active one.
ActivatePrevious Activates the MDI child preceding the currently active one.
ArrangeIcons Arranges any iconized (minimized) MDI child windows.
Cascade Arranges the MDI child windows in a cascade.
Create Used in two-step frame construction.
GetActiveChild Returns a pointer to the active MDI child, if there is one.
GetClientWindow Returns a pointer to the client window.
GetWindowMenu Returns the current MDI Window menu.
IsTDI Returns whether the MDI implementation is tab-based.
OnCreateClient Override this to return a different kind of client window.
SetWindowMenu Replace the current MDI Window menu.
Tile Tiles the MDI child windows either horizontally or vertically depending on whether orient is HORIZONTAL or VERTICAL .

api Class API


class MDIParentFrame(Frame)

An MDI (Multiple Document Interface) parent frame is a window which can contain MDI child frames in its client area which emulates the full desktop.

Possible constructors:

MDIParentFrame()

MDIParentFrame(parent, id=ID_ANY, title='',
               pos=DefaultPosition, size=DefaultSize,
               style=DEFAULT_FRAME_STYLE|VSCROLL|HSCROLL, name=FrameNameStr)

Methods


__init__(self, *args, **kw)

overload Overloaded Implementations:


__init__ (self)

Default constructor.

Use Create for the objects created using this constructor.


__init__ (self, parent, id=ID_ANY, title=’‘, pos=DefaultPosition, size=DefaultSize, style=DEFAULT_FRAME_STYLE|VSCROLL|HSCROLL, name=FrameNameStr)

Constructor, creating the window.

Notice that if you override virtual OnCreateClient method you shouldn’t be using this constructor but the default constructor and Create as otherwise your overridden method is never going to be called because of the usual C++ virtual call resolution rules.

Parameters:
  • parent (Window) – The window parent. Usually is None.
  • id (int) – The window identifier. It may take a value of ID_ANY to indicate a default value.
  • title (string) – The caption to be displayed on the frame’s title bar.
  • pos (Point) – The window position. The value DefaultPosition indicates a default position, chosen by either the windowing system or wxWidgets, depending on platform.
  • size (Size) – The window size. The value DefaultSize indicates a default size, chosen by either the windowing system or wxWidgets, depending on platform.
  • style (long) – The window style. Default value includes HSCROLL and VSCROLL styles.
  • name (string) – The name of the window. This parameter is used to associate a name with the item, allowing the application user to set Motif resource values for individual windows.

Under wxMSW, the client window will automatically have a sunken border style when the active child is not maximized, and no border style when a child is maximized.

See also

Create , OnCreateClient



ActivateNext(self)

Activates the MDI child following the currently active one.

The MDI children are maintained in an ordered list and this function switches to the next element in this list, wrapping around the end of it if the currently active child is the last one.

See also

ActivatePrevious


ActivatePrevious(self)

Activates the MDI child preceding the currently active one.

See also

ActivateNext


ArrangeIcons(self)

Arranges any iconized (minimized) MDI child windows.

This method is only implemented in MSW MDI implementation and does nothing under the other platforms.

See also

Cascade , Tile


Cascade(self)

Arranges the MDI child windows in a cascade.

This method is only implemented in MSW MDI implementation and does nothing under the other platforms.

See also

Tile , ArrangeIcons


Create(self, parent, id=ID_ANY, title='', pos=DefaultPosition, size=DefaultSize, style=DEFAULT_FRAME_STYLE|VSCROLL|HSCROLL, name=FrameNameStr)

Used in two-step frame construction.

See MDIParentFrame for further details.

Parameters:
  • parent (Window) –
  • id (int) –
  • title (string) –
  • pos (Point) –
  • size (Size) –
  • style (long) –
  • name (string) –
Return type:

bool

GetActiveChild(self)

Returns a pointer to the active MDI child, if there is one.

If there are any children at all this function returns a not None pointer.

Return type: MDIChildFrame

GetClientWindow(self)

Returns a pointer to the client window.

Return type: MDIClientWindow

See also

OnCreateClient


GetWindowMenu(self)

Returns the current MDI Window menu.

Unless FRAME_NO_WINDOW_MENU style was used, a default menu listing all the currently active children and providing the usual operations (tile, cascade, ...) on them is created automatically by the library and this function can be used to retrieve it. Notice that the default menu can be replaced by calling SetWindowMenu .

This function is currently not available under OS X.

Return type: Menu
Returns:The current Window menu or None.

static IsTDI()

Returns whether the MDI implementation is tab-based.

Currently only the MSW port uses the real MDI. In Mac ports the usual SDI is used, as common under this platforms, and all the other ports use TDI implementation.

TDI-based MDI applications have different appearance and functionality (e.g. child frames can’t be minimized and only one of them is visible at any given time) so the application may need to adapt its interface somewhat depending on the return value of this function.

Return type:bool

OnCreateClient(self)

Override this to return a different kind of client window.

If you override this function, you must create your parent frame in two stages, or your function will never be called, due to the way C++ treats virtual functions called from constructors. For example:

frame = MyParentFrame()
frame.Create(parent, myParentFrameId, "My Parent Frame")

You might wish to derive from MDIClientWindow in order to implement different erase behaviour, for example, such as painting a bitmap on the background.

Note that it is probably impossible to have a client window that scrolls as well as painting a bitmap or pattern, since in OnScroll, the scrollbar positions always return zero.

Return type: MDIClientWindow

See also

GetClientWindow , MDIClientWindow


SetWindowMenu(self, menu)

Replace the current MDI Window menu.

Ownership of the menu object passes to the frame when you call this function, i.e. the menu will be deleted by it when it’s no longer needed (usually when the frame itself is deleted or when SetWindowMenu is called again).

To remove the window completely, you can use the FRAME_NO_WINDOW_MENU window style but this function also allows to do it by passing None pointer as menu.

The menu may include the items with the following standard identifiers (but may use arbitrary text and help strings and bitmaps for them):

  • ID_MDI_WINDOW_CASCADE
  • ID_MDI_WINDOW_TILE_HORZ
  • ID_MDI_WINDOW_TILE_VERT
  • ID_MDI_WINDOW_ARRANGE_ICONS
  • ID_MDI_WINDOW_PREV
  • ID_MDI_WINDOW_NEXT All of which are handled by MDIParentFrame itself. If any other commands are used in the menu, the derived frame should handle them.

This function is currently not available under OS X.

Parameters:menu (Menu) – The menu to be used instead of the standard MDI Window menu or None.

Tile(self, orient=HORIZONTAL)

Tiles the MDI child windows either horizontally or vertically depending on whether orient is HORIZONTAL or VERTICAL .

This method is only implemented in MSW MDI implementation and does nothing under the other platforms.

Parameters:orient (Orientation) –

Properties


ActiveChild

See GetActiveChild


ClientWindow

See GetClientWindow


WindowMenu

See GetWindowMenu and SetWindowMenu

© Copyright 2012, Andrea Gavana. Created using Sphinx 1.2pre.