Saving MDI layout

Yes it is. You hammer through the document list and save the document/frame/view information for each. This is a snippet of what our XML 'workspace' file looks like:

<Documents Count="2">
  <Document0 docpath=".\\ELB Sale Pad 2.ksp" docguid="<docprogid1>" doctitle="ELB Sale Pad 2.ksp" docapplet="Sale Pad">
    <Frames Count="1">
      <Frame0 paneid="0">
        <Placement showcmd="1" minposition="-1, -1" maxposition="-4, -23" normalposition="0, -8, 1019, 268"/>
        <Views Count="1">
          <View0 isactive="0" isvisible="1"/>
        </Views>
      </Frame0>
    </Frames>
  </Document0>
  <Document1 docpath=".\\ELB Analysis Pad 2.kap" docguid="<docprogid2>" doctitle="ELB Analysis Pad 2.kap" docapplet="Analysis Pad">
    <Frames Count="1">
      <Frame0 paneid="0">
        <Placement showcmd="1" minposition="-1, -1" maxposition="-1, -1" normalposition="1, 266, 1020, 591"/>
        <Views Count="1">
          <View0 isactive="1" isvisible="1"/>
        </Views>
      </Frame0>
    </Frames>
  </Document1>
</Documents>

The Placement tag is done by deriving a new class from CXTPWindowPos that serialises via DoPropExchange() - why that is there I don't know...

The docguid attribute is the document template progid-like string - necessary only if you use multiple document templates.

The paneid attribute is necessary only if you dock CView derivatives.

The only other thing to note is the path is saved relative to the 'workspace' file itself - that way they can all be picked up and moved/copied to other directories without having to worry about absolute path nonsense.