|
From: Thomas A. <th...@xt...> - 2010-09-24 19:40:12
|
On Fri, Sep 24, 2010 at 10:08:52PM +0300, Mikhael Goikhman wrote:
> I am not very strong about this issue, although I prefer a less
> destructive Delete in buttons than Close. But maybe I miss some
> serious use case that caused to such change. What do others think?
This is one of those expose problems which X11 inherently presents to the
user. As a user, I don't care if my window is deleted or destroyed -- just
that it goes away when I ask it to close. The problem there though, is
because there's these two very different methods, I start to _have_ to care
more if said application suddenly throws a wobbly and sits there IO bound,
hosing my machine with 100% CPU.
But that's a side-issue to fvwm-themes appearing to Do The Right Thing (tm)
which is ultimately to close my window. I currently have no wa to do that
if the application in question doesn't listen to WM_DELETE, and as a user I
am left baffled and confused -- I just want the window to close.
Get fvwm-themes to do The Right Thing (tm) -- at least Close is graceful in
trying Delete before Destroy -- and that's the way it should be. We're not
losing out here, we're just ensuring those Brain Dead (tm) applications go
away. Any side-effects coming from a WM_DESTROY aren't FVWM's fault, and
legitimately, FVWM is still Doing The Right Thing (tm) -- such observations
in Brain Dead Applications (tm) aren't anything to do with us. After all,
we tried to Do The Right Thing (tm) via Close, and that's the best we can
and /should/ do. :)
I'd bet you no one's going to even notice the change. :)
I think with all these trademarks I'm issuing here, I could make a nice tid
sum of money on the side... ;)
-- Thomas Adam
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
|