> > * As with the window-shade packets I pointed to earlier this week, the
> > * standard 3 args are missing from the start of this packet.
>
> I don't see why you insist to consider that a problem. There simply exist
> *several* packet types. Yes, the world of interface library making would be a
> much easier place if there was only one type, but... ;-)
Why do I find this a problem. Hmmmm.
How about this: all of the packets which contain data specific to one managed
window have this triple. Of course M_DESK doesn't, or M_STRING. But if a packet
pertains to a specific window, all other packet types have the triple. Except
M_MINI_ICON (unless you chose not to apply my patch to the windowshade packets,
in which case you have three packets that don't). The module docs not only
frequently refer to this triple is the means of identifying fvwm-managed
windows, it specifically refers to the third element, the "internal index"
(actually the hex representation of the struct's memory address), as well-
suited for use as an index of sorts for programs that list and index windows.
Yes, there are several packet types (more accurately, each packet is its own
type, there are several classes into which packets fall). But M_MINI_ICON has
a relationship to a specific subset of the packet types, and as such should
conform to them.
> Sigh,
Indeed.
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 Thu Apr 17 1997 - 17:44:40 BST