> OK, but consider for a bit the possibility that you might like to tell a
> module go away without quitting FVWM. It seems better to ask the module to
> go away, rather than just yanking its input stream. An EXIT packet
> wouldn't necessarily tell the module that FVWM is going away, but only that
> the module should go away.
>
> I'm assuming, of course, that there isn't already an EXIT packet. It's
> been a while since I hacked on FVWM modules.
>
> Of course, modules should still properly handle FVWM croaking anyway.
I've gotten around my earlier problems by looking for an error return from
sysread (the perl equivalent of C's read(), since perl's read is actually
build on the buffered-IO layer) and (for now) not even using select() to poll
my fd's. I am also inquiring on the perl list if there are any known bugs with
select on HP's (luckily, we have a guy from HP support on the list).
So I am handling exits all right, and will probably add in a special handler
category in my perl module to allow programmers to respond to the exit. But
I still think M_EXIT would be a good idea:
Packet:
word 1 :- Window ID \
word 2 :- Fvwm Frame ID > These three are standard
word 3 :- Fvwm window ID /
word 4 :- Restart: 0 if Fvwm is really quitting, 1 if Fvwm is doing a
Restart (as is denoted by the flag to Done() in fvwm.c)
Randy
--
===============================================================================
Randy J. Ray -- U S WEST Technologies IAD/CSS/DPDS Phone: (303)595-2869
Denver, CO rjray_at_uswest.com
"It's not denial. I'm just very selective about the reality I accept." --Calvin
===============================================================================
--
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 - 21:23:28 GMT