4 Jul
2003
4 Jul
'03
4:56 p.m.
hi,
perhaps an abstraction with a [route $1 $2...] in it would be a more straightforward choice?
If not, a [coll] or similar driving a [gate <nouts>] seems like a router flexible enough in most cases.
Krzysztof
slow wrote:
hi
I'm using netreceive and try to use a single subpatch that could receive certain messages on different machines...
I wonder if one of you did modify the ROUTE object in order to dynamically change the routing arguments...