Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!agate!scam!scott
From: scott@scam.Berkeley.EDU (Scott Silvey)
Newsgroups: comp.windows.x
Subject: WM_SAVE_YOURSELF
Message-ID: <1991Jan22.064227.4656@agate.berkeley.edu>
Date: 22 Jan 91 06:42:27 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: scott@xcf.berkeley.edu
Organization: UC Berkeley Experimental Computing Facility
Lines: 25

I posted about a week ago about the WM_SAVE_YOURSELF protocol (ICCC).

I am having trouble getting my programs to respond to this message properly
  and I was wondering if anyone out there knows how to do this.

My understanding of the ICCCM is that all one needs to do is to "tickle" the
  WM_COMMAND property on the client window by setting it to "" (null string).

Is this correct?  When I do this, my callback runs but the client window 
  is immediately unmapped by mwm and when the callback returns, the application
  is killed.

I would like to know how to avoid being blown away by this protocol if the
  user decides to avoid it.

Thanks.

PS: I included a sample program in my earlier posting...

-- 
/-----------------------------------------------------------------------------\
| Scott Silvey           | Ronald Reagan on Pac Man:                          |
| scott@xcf.berkeley.edu | "Someone told me it was a round thing that gobbles |
| Flames to /dev/null.   |  up money, but I thought that was Tip O'Neill."    |
\-----------------------------------------------------------------------------/