Hi Günter,
my concerns are exactly the same as your's. My thoughts go along the following lines:
add a right inlet to send the way you suggest (which wouldn't break anything).
if send gets initialized without argument, the first element of a received list is the target. This could break things although it seems rather unlikely that anybody ever used send without arguments, as any message received in such an object would get discarded.
What do you think? I can apply the changes and post the patch against x_connective.c to the list (is that the way to go?)
-- Orm
Am 10. August 2006, 18:44 Uhr (+0200) schrieb geiger:
On Thu, 10 Aug 2006, Orm Finnendahl wrote:
Hi all,
does anybody know a way to send arbitrary length messages to arbitrary receivers? I would like to send OSC messages of variable length to pd, specifying the receiver in the first element of the message. It has to be completely dynamic as I want to create pd subpatchers dynamically, so OSCroute won't work.
It would be possible, if e.g. the send object allowed for a set message (or have a right inlet for setting the receiver), or if it was possible to use message boxes with Dollarsigns for arbitrary length messages.
Before patching pd's send I thought to better ask for a standard way to get this done.
Hi Orm,
I recently had the same problem. There is an external send13 (in ext13) that accepts a set message. This solution is bad, because then you can't send "set" messages anymore. I think the best thing would be to have a second inlet to send, if you go that way it would be great if you could put your solution on the patch tracker.
Günter
PS: I couldnt find a standard way either ... maybe someone else knows.