Hi Rob,
thanks a lot for your long answer. I see that I misunderstood
fvwm's behavior.
> While it would be nice for fvwm to send a delete message, and then wait
> to see if the window goes away, and then destroy the window if its not
> responding, this is difficult to code up. What if the program pops up
> a confirm dialog before going away? The delay could be indefinite.
You're right. I can see the problem.
Chuck, you can take this off of the TO-DO list again. But maybe it would
make sense to put Rob's answer into the FAQ.
> The correct thing to put in your menu, is a simple "Close" this will
> correctly remove all windows, except those that understand "Delete" and
> are misbehaving (crashing, poorly written, whatever). To handle the case
> of a misbehaving window, have a separate item "Destroy" which you invoke only
> if the window doesn't respond to "Close"
I now changed Delete to Close and got the behavior I was wishing to
have. I added a special menu item and keyboard shortcut for the
destroy option, in case Close doesn't work.
Thanks again,
Andy.
___________________________________________________________________________
Andy Spiegl, Institute for Applied Mathematics
University of Technology, Muenchen, Germany
E-Mail: Spiegl_at_Appl-Math.TU-Muenchen.de
http://www.appl-math.tu-muenchen.de/~spiegl/
Above all else - sky.
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Dec 20 1995 - 10:35:53 GMT