Here I go again with another module packet suggestion. This time if it gets
added I promise to document it in the modules.tex :-).
I've had a request to make is so that FvwmIconMan could follow the fvwm window
list order exactly. This is currently quite difficult to do as the list order
changes silently at various times, and there's no way to really tell from
outside of fvwm. For example, my perusal of the fvwm code shows that FlipFocus
changes the window list order, while Focus does not. There's no way for a
module to tell which of these happened from watching the messages from fvwm.
So, my proposal is a new packet type which keeps modules informed of any
changes to the window list order.
Other modules, current and potential, could benefit from this as well.
This brings up a more general class of features. Fvwm maintains some important
data structures, and it would be nice if modules could be able to access them,
either in a read-only or read-write fashion. A packet listing whatever changes
have occured to the window list order is a simple way of implementing
read-only access to a portion of the window list. Can anyone think of other
things in this class?
--
Brady Montz
bradym_at_cs.arizona.edu
--
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 Tue May 13 1997 - 12:06:42 BST