On 8 May, Randy J. Ray wrote:
>> > 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.
>
> M_STRING is a broadcast packet, and thus is not tied to a specific window.
True, but you might be able to use a hack like this (I haven't tried it
out, but it oughta work). Create a function:
AddToFunction MySendToModule "I" SendToModule $0 $w $1
(or something like that) and call MySendToModule instead. Then have
the pseudo-rxvt parse the window-id out of the string, and ignore the
message if it's not that instance's id.
This is just an idea - I certainly haven't tested it. Is $w even still
implemented in 2.0.45?
--Chris
--
Prudence, indeed, will dictate that governments long established
should not be changed for light and transient causes; and accordingly
all experience hath shown that mankind are more disposed to suffer,
while evils are sufferable, than to right themselves by abolishing the
forms to which they are accustomed.
-- Thomas Jefferson, Prologue, "Declaration of Independence"
______________________________________________________________________
Chris Laas: Unix, C++, Perl, Tcl/Tk / mailto:chrisl_at_cybercom.net
Limit[tech->Inf](words/acronyms)==0 / http://www.cybercom.net/~chrisl/
--
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 - 20:13:16 BST