Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sunybcs!boulder!stan!ninja!toml
From: toml@ninja.Solbourne.COM (Tom LaStrange)
Newsgroups: comp.windows.x
Subject: Re: TWM, KillClient versus DestroyWindow
Message-ID: <1989Dec5.144741.20097@Solbourne.COM>
Date: 5 Dec 89 14:47:41 GMT
Sender: news@Solbourne.COM
Organization: Solbourne Computer, Inc.
Lines: 20

> affecting the other windows.  But TWM's f.destroy function seems to do a
> KillClient, which it seems I can't recover from.  This seems like a fairly
> extreme policy.  I'd like to be able to negotiate saving window data with
> the user, and continue processing other windows.
> 
> How come TWM doesn't simply call XDestroyWindow on the appropriate Window ID?
> Wouldn't I then just get a Window Destroyed event on that window, and continue
> operations for my other windows?  Is this just a TWM quirk, or is this an
> ICCCM reality that I must accept?

The R4 version of twm supports both the WM_SAVE_YOURSELF and
WM_DELETE_WINDOW protocols as set forth in the ICCCM.  This will be
the proper way to tell the window manager to not use XKillClient.

--
Tom LaStrange

Solbourne Computer Inc.    ARPA: toml@Solbourne.COM
1900 Pike Rd.              UUCP: ...!{boulder,sun}!stan!toml
Longmont, CO  80501