> > SendToModule FvwmRxvt <str>
> >
> > Let's say the user has 3 of these rxvt instances active when he clicks the
> > button on one of them... all 3 will get the packet.
>
> I realize that. I was hopping that the information send with the
> packet contained the window ID of the window the button was clicked
> on. If that information was also sent, it would make the
> SendToModule function much more powerfull for the case of multiple
> modules being used.
The window ID is only sent to a module when the module is executed. It is sent
as one of the command-line arguments. The value is zero if the module was not
started in the context of an existant window (from a titlebar button or some
such), that is, if it was launched from the dot-file or from a root-window
menu.
The only packets that contain window identification are those which contain
data specific to a window-- iconification, configuration, resource names, etc.
M_STRING is a broadcast packet, and thus is not tied to a specific window.
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 May 08 1997 - 12:19:33 BST