IJ>
  > What a creative change in subject name :-)
IJ>

  Don't you hate boring repetitious subject lines as well ?  (-:

IJ>
  >  JdeBP> The notes for WM_QUIT in the PM Reference in your toolkit will
  >  JdeBP> tell you the rest.
  >
  > No it doesn't. The documentation of WM_CLOSE, WM_SAVEAPPLICATION and
  > WM_QUIT is unusually vague.
IJ>

  It was fine for me.

IJ>
  > How to handle close or system shutdown "correctly": (pseudocode)
  >
  > WM_CLOSE:
  >   if 
  >     // prompt user, save application, then
  >     pass the wm_close to DefWindowProc
  >   else
  >     pass the wm_close to DefWindowProc
IJ>

  BZZZT!  You lose 50 points.  (-:

  Go back to the PM reference.  Look under "Default processing" for
  WM_CLOSE and think about what happens when your application has
  multiple windows.

IJ>
  > WM_QUIT:
  >   The application should call DestroyWindow for the window(s) it has
  >   created, and terminate.
IJ>

  Some applications place their "Do you want to save settings?" logic
  after their message loop has exited due to a WM_QUIT.

  You can actually differentiate between a WM_QUIT as sent by a system
  shutdown, and a WM_QUIT as sent by a WM_CLOSE by inspecting the window
  handle in the QMSG structure.   A system shutdown sets it to
  NULLHANDLE, whereas a WM_CLOSE (or a shutdown sent from the Window
  List), fills in an actual window handle.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02