NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/windows/x/14603

Text File | 1992-07-29 | 2.0 KB | 41 lines

Newsgroups: comp.windows.x
Path: sparky!uunet!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
From: [e-mail] (der Mouse)
Subject: Re: Kills from Window Manager
Message-ID: <[e-mail]>
Organization: McGill Research Centre for Intelligent Machines
References: <[e-mail]> <[e-mail]>
Date: Thu, 30 Jul 92 00:45:40 GMT
Lines: 31

In article <[e-mail]>, [e-mail] (Barry Margolin) writes:
> In article <[e-mail]> [e-mail] (der Mouse) writes:
>> In article <[e-mail]>, [e-mail] (Barry Margolin) writes:
>>> When I use f.delete on windows of clients that don't implement the
>>> protocol, twm beeps at me.
>> In that case, then you need to fix twm or your menus: [...] or your
>> menus, if f.delete is supposed to be "send WM_DELETE_WINDOW if
>> requested" (because that's not the operation you want).
> The twm man page [says that the latter is the case].

> I wasn't complaining about the beep; I think it's the right thing.  I
> don't know about you, but I don't want my window manager
> automatically upgrading an attempt to delete a single window into an
> operation that will probably crash the application

Why not?  If the application doesn't participate in WM_DELETE_WINDOW,
it is telling the window manager that it's perfectly willing to be
XKillClient()ed.  (Remember, we were talking about simple apps that
have only one top-level window and need to do no particular cleanup
when dying.  An application that does multiple top-level windows but
still doesn't do WM_DELETE_WINDOW is IMO broken badly enough that I'm
willing to ignore its existence.)

None of this affects, as far as I can see, my point that there is no
need for a simple application (as defined in my parenthetical note last
paragraph) to participate in WM_DELETE_WINDOW.

                    der Mouse

                [e-mail]