<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE erlref SYSTEM "erlref.dtd">

<!-- THIS FILE IS GENERATED DO NOT EDIT -->


<erlref>
<header>
  <copyright>
    <year>2020</year>
    <holder>wxWidgets team.</holder></copyright>
  <legalnotice>Licensed under the wxWindows Free Documentation Licence, Version 3
  </legalnotice>
  <title>wxMDIClientWindow</title>
</header>
<module>wxMDIClientWindow</module>
<modulesummary>Functions for wxMDIClientWindow class</modulesummary>
<description><p>An MDI client window is a child of <seeerl marker="wxMDIParentFrame"><c>wxMDIParentFrame</c></seeerl>, and manages zero or more <seeerl marker="wxMDIChildFrame"><c>wxMDIChildFrame</c></seeerl> objects.
      </p><p> The client window is the area where MDI child windows exist. It doesn't have to cover the whole parent frame; other windows such as toolbars and a help window might coexist with it. There can be scrollbars on a client window, which are controlled by the parent window style.
      </p><p>The <seeerl marker="wxMDIClientWindow"><c>wxMDIClientWindow</c></seeerl> class is usually adequate without further derivation, and it is created automatically when the MDI parent frame is created. If the application needs to derive a new class, the function <c>wxMDIParentFrame::OnCreateClient()</c> (not implemented in wx) must be overridden in order to give an opportunity to use a different class of client window.
      </p><p>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.
      </p><p>See: <seeerl marker="wxMDIChildFrame"><c>wxMDIChildFrame</c></seeerl>, <seeerl marker="wxMDIParentFrame"><c>wxMDIParentFrame</c></seeerl>, <seeerl marker="wxFrame"><c>wxFrame</c></seeerl>
      </p>
  <p>This class is derived (and can use functions) from: 
    <seeerl marker="wxWindow"><c>wxWindow</c></seeerl> <seeerl marker="wxEvtHandler"><c>wxEvtHandler</c></seeerl></p>
  
  <p>wxWidgets docs: <url href="https://docs.wxwidgets.org/3.1/classwx_m_d_i_client_window.html">wxMDIClientWindow</url></p>
  </description>
<datatypes><datatype><name name="wxMDIClientWindow"/></datatype></datatypes>

<funcs>
  <func>
    <name name="new" arity="0" clause_i="1" since=""/>
    <fsummary>Default constructor. </fsummary>
    <desc><p>Default constructor. 
      </p><p>Objects of this class are only created by <seeerl marker="wxMDIParentFrame"><c>wxMDIParentFrame</c></seeerl> which uses the default constructor and calls <seemfa marker="#createClient/3"><c>createClient/3</c></seemfa> immediately afterwards. 
      </p></desc>
  </func>
  
  <func>
    <name name="createClient" arity="2" clause_i="1" since=""/>
    <fsummary>See: <c>createClient/3</c></fsummary>
  </func>
  
  <func>
    <name name="createClient" arity="3" clause_i="1" since=""/>
    <fsummary>Called by <c>wxMDIParentFrame</c> immediately after creating the client window. </fsummary>
    <desc><p>Called by <seeerl marker="wxMDIParentFrame"><c>wxMDIParentFrame</c></seeerl> immediately after creating the client window. 
      </p><p>This function may be overridden in the derived class but the base class version must usually be called first to really create the window.
      </p></desc>
  </func>
  
  <func>
    <name name="destroy" arity="1" clause_i="1" since=""/>
    <fsummary>Destructor</fsummary>
    <desc><p>Destroys the object.</p></desc>
  </func>
  </funcs>
</erlref>
