On Fri, 14 Mar 1997 18:21:13 EST, "Barry A. Warsaw" writes:
>
>>>>>> "RJR" == Randy J Ray <rjray_at_uswest.com> writes:
[...]
> RJR> So perhaps a good idea would be a packet type of M_FVWM_EXIT
> RJR> (or just M_EXIT, or similar) that is sent to all modules
>
>This might be a cleaner (and better documented) way of signalling
>termination to the modules. Although the current approach seems to
>work for me, this addition probably doesn't burden Fvwm much.
On the other hand, if a module is relying on a special message to tell
it when fvwm is going away, it's not going to do The Right Thing if fvwm
doesn't exit cleanly (eg. if the X server shuts down, killing fvwm
before it can send the M_EXITs to its children).
Modules should be able to detect and deal with their pipes being closed
unexpectedly; adding a redundant (but less reliable) mechanism to signal
that fvwm is terminating would make it *less* clean.
-- People shouldn't think that it's better to have
Dan Astoorian loved and lost than never loved at all. It's
http://www.utopia.csas.com not, it's better to have loved and won. All
djast_at_utopia.csas.com the other options really suck. --Dan Redican
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Fri Mar 14 1997 - 17:48:55 GMT