>>>>> "RJR" == Randy J Ray <rjray_at_uswest.com> writes:
RJR> Well, this probably won't work for a lot of other
RJR> event-driven applications besides my own exploration with
RJR> Perl and Tk. A C application using the Xt or Xm toolkits is
RJR> likely to pass it's control to an event loop, and rely on
RJR> bound callbacks for handling all eventualities.
My own Python/Tk modules uses tkinter.createfilehandler()
(i.e. Tcl_CreateFileHandler()) to dispatch on data available from the
fd Fvwm is writing to. Seems like this works well, and my module does
know when Fvwm is exiting or restarting. When I wrap a try/finally
around my call to Tk's mainloop, I can see that when I restart Fvwm,
my finally clause gets tripped after Tk's mainloop is terminated.
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.
-Barry
--
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:18:46 GMT