shap@sequent.UUCP (Shap Shapiro) (08/23/90)
Does anyone out there know of a way for a motif application to catch the fact
that it is being shutdown via an XKillClient and perform some cleanup before
going away?
Thanks,
Shap
----------------------------------------------------------------------
Shap Shapiro | Sequent Computer Systems |
| 15450 SW Koll Parkway |
{uunet|ogicse|tektronix}!sequent!shap | Beaverton, OR 97006 |
sequent!shap@cse.ogi.edu | (503) 526-4158 or 626-5700 |
shap@sequent.UUCP | fax (503) 526-5795 |
----------------------------------------------------------------------shap@sequent.UUCP (Shap Shapiro) (08/24/90)
Just a clarification on my question about catching an XKillClient in a Motif
application. This has nothing to do with MWM. I am basically asking if there
is some standard mechanism that an application should use to perform some
cleanup operations when the connection to that client is forcibly closed. Do I
need to install an error handler? Is there some destroy callback that can be
used?
Thanks in advance, I will post any solutions I get to the net.
Shap
----------------------------------------------------------------------
Shap Shapiro | Sequent Computer Systems |
| 15450 SW Koll Parkway |
{uunet|ogicse|tektronix}!sequent!shap | Beaverton, OR 97006 |
sequent!shap@cse.ogi.edu | (503) 526-4158 or 626-5700 |
shap@sequent.UUCP | fax (503) 526-5795 |
----------------------------------------------------------------------