On 7 May 97 at 15:14, Randy J. Ray <Randy J. Ray <rjray_at_uswest.com>>
wrote:
> The M_STRING packet has 4 values in the body: 3 zeros, followed by the string
> itself. It gets sent via:
>
> SendToModule <pat> <str>
>
> where <pat> is a pattern specifiying which module or modules receive <str>.
> The problem here is that you are considering turning rxvt into a module, for
> arguments' sake we'll call it FvwmRxvt, which will be sent some string via a
> button on the title bar. So that button is bound to do:
>
> 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.
I will have to look into Chuck's suggestion of using xse. I have not
heard of that program before. Thanks for the help and suggestions.
Richard A. Guay
Network Administrator and ASIC Design Engineer
ASIC International Inc.
rag_at_asicint.com
http://www.asicint.com
--
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 - 10:51:32 BST