Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!fxgrp!mikew
From: mikew@fx.com (Mike Wexler)
Newsgroups: comp.windows.x
Subject: Re: WM_SAVE_YOURSELF
Message-ID: <1991Feb4.174841.4272@fxgrp.fx.com>
Date: 4 Feb 91 17:48:41 GMT
References: <1991Jan22.064227.4656@agate.berkeley.edu> <100920280@hpcvlx.cv.hp.com> <1991Jan25.201354.17242@agate.berkeley.edu> <968@redford.UUCP>
Sender: news@fxgrp.fx.com (News)
Reply-To: mikew@fx.com
Organization: FXD/Telerate, Mountain View, CA
Lines: 20

bill@polygen.uucp (Bill Poitras) writes:

>In article <1991Jan25.201354.17242@agate.berkeley.edu> scott@xcf.berkeley.edu writes:
>>MY QUESTION IS: How do I prevent my application from getting blown away by
>>  the WM_SAVE_YOURSELF mechanism?  Is this even possible according to ICCC?
>>  (I thought it was, but perhaps I am reading ICCCM wrong?).

>I don't think you prevent WM_SAVE_YOURSELF from blowing you away. You
>have to maken sure that WM_PROTOCOLS window property is not set for 
>your application.  In Motif, you should make sure that WM_SAVE_YOURSELF 
>is not being set.  For further information, consult the Motif Programmer's
>Guide.  In the version 1.0 manual, this is section 8.8.2 Protocol Manager 
>Functions.
The proper thing for him to have the WM_DELETE_WINDOWS protocol in his
WM_PROTOCOLS property to handle his dialog box asking the user to
save his changes. He SHOULD have WM_SAVE_YOURSELF in his WM_PROTOCOLS
if he supports that protocol, whether or not he is targeting Motif. This
works fine and is very useful even under Motif if you have appropriate tools.
--
Mike Wexler (mikew@fx.com)