Re: Huge Batch Reply: Lars

[Scott Goehring <scott poverty bloomington in us>]

"Dan \"Effugas\" Kaminsky" <effugas@best.com> writes:

Dan> Because it makes logical sense.  The menuprint is owned by the
Dan> *system*, not by the application.  In Windows right now when a
Dan> program crashes I need to press control-alt-delete and try to
Dan> find that program's entry, and kill that.  It'd be much nicer to
Dan> have a button that works when even the app doesn't and be able to
Dan> force quit.

We can put such a button on a WM title bar because WM buttons are the
WM's responsibility.  However, putting a button in the application's
window is impossible, because the application would be responsible for
it, and if the app is not responding, it can't respond to a button
press.  However, WM issues are beyond the scope of this project
because GNOME does not mandate any specific WM.  You'll have to settle
for a requirement that GNOME apps handle WM_DELETE messages
appropriately.

This aside, the problem of apps crashing in X and leaving windows
hanging is _very_ rare.  I suppose a very badly coded app could spin
without revisiting the main loop, thereby locking up without losing
its X connection.  There is no way that an app can recover from this
situation, obviously; it's the WM's job, and every WM I've ever seen
offers some means to do it.  But, as I've stated, WM design issues are
beyond the scope of this project.