> Sorry, I didn't know M_MINI_ICON was window-specific (I have to add these new
> packet types to fvwm.py one of these days). The "windowshade" ones must be
> window-specific for sure!
Yes-- the purpose of M_MINI_ICON is to inform a module of a mapping between
mini's and windows. Each window can conceivably have one. Part of the debate
over the packet format is based on the fact that the current implementation
sends the X server pixmap ID, which is not useful to non-C modules (which means
you actually have a stake in this :-).
> my fvwm.py needs it (keeps track of windows, of course - I chose the wid for
> it). I don't have fvwm sources handy, so I don't know what M_MINI_ICON is
> supposed to do, but if it refers to a single window, the packet ought to carry
> its id. If you say that the windowshade ones don't, that's strange... What are
> the modules supposed to do with them then?
>
> (I'll search for your patch)
The windowshade packets (M_WINDOWSHADE/M_DEWINDOWSHADE) only contained the
X window ID for the main window. My patch merely has them contain the regular
three values.
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 Apr 18 1997 - 17:54:36 BST