Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!olivea!oliveb!veritas!amdcad!sun!quintus!pds
From: pds@quintus.UUCP (Peter Schachte)
Newsgroups: comp.windows.x
Subject: Re:  Can an application know a DESTROY/KILL is applied on itself?
Message-ID: <1476@quintus.UUCP>
Date: 25 Jan 91 22:25:52 GMT
References: <9101220259.AA12732@lightning.McRCIM.McGill.EDU>
Reply-To: pds@quintus.UUCP (Peter Schachte)
Organization: Quintus Computer Systems, Inc.
Lines: 18

In article <9101220259.AA12732@lightning.McRCIM.McGill.EDU> mouse@lightning.mcrcim.mcgill.EDU writes:
>> The DestroyNotify in Xlib doesn't work because
>Because DestroyNotify is for something else: notifying applications of
>window destruction.  And as you noticed, while the window is destroyed
>by the forced connection close, the client can't get the event.

I guess it's kind of late for this, but why didn't the ICCCM
establish the convention that window managers just destroy a top-level window
when they want to get rid of it?  Applications would have to watch for
destroy events on their top-level windows.  That would be quite easy to
do, and would work much better for multi-window applications, where you
don't want the whole application killed just because the WM wants to
close one window.

-- 
-Peter Schachte
pds@quintus.com
...!{uunet,sun}!quintus!pds