AT>
  > So I had to get crazy  to subclass all frame controls windows (FID_MENU,
  > FID_SYSMENU, and so on), I had to write my own WM_TILE, WM_ARRANGE command
  > functions.... it was ugly!
AT>

  It is also unnecessary.  I've maintained an application that does MDI on
  OS/2 Presentation Manager, and there wasn't any need to subclass any of
  the frame controls at all.  Tiling and arranging are simplicity
  themselves, being little more than calls to Win*EnumWindows and
  WinSetMultWindowPos.

  Even implementing the "bare minimum" for an OS/2 MDI application gives a
  reasonably clean and functional interface.  Most things "just work",
  with no additional code required.  Compare this with Windows, and
  problems like providing individual menus for individual child windows
  (with OS/2 PM, you just put the menu in the resource definition for the
  child window, and it works), or giving child windows anything other than
  sizeable borders (with OS/2 PM, you can just specify a border type and
  it works).

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.01