[PD-dev] OSCroute "set" feature request

d.lj jdl at xdv.org
Wed Nov 10 20:42:29 CET 2004


yolla

just a quick quest: single or multi element OSCroute instances?

i.e. implication of multi element set: changing number of outlets on a
living object, e possibile?

maybe tune pattern matching so multi element set can be synomymized with

|set (/bli|/bla) <


bst, opt/jdl/etc

[B. Bogart]->[[PD-dev] OSCroute "set" feature request]->[04-11-07 23:07]

 |Hello OSCx developer(s),
 |
 |I see that "set" message has been added to the little todo list at the start of
 |OSCroute.c. Has there been any progress on this front?
 |
 |I'm working on a lot of complex collections of abstractions using memento and
 |really need to be able to specify the route name via message rather than by
 |argument. The reason being is that I'm working on an infrastructure so that the
 |abstractions don't have to be named individually, they are automatically named
 |by thier position in the structure. In order to name dynamically I need to be
 |able to route OSC message dynamically!
 |
 |I would really appreciate this feature, and would be happy to get any
 |development code that represents a stab at the problem to work on myself.
 |
 |Thanks for all your work.
 |
 |Ben
 |
 |
 |_______________________________________________
 |PD-dev mailing list
 |PD-dev at iem.at
 |http://iem.at/cgi-bin/mailman/listinfo/pd-dev
 |------------ Output from gpg ------------
 |gpg: Signature made Mon Nov  8 05:07:09 2004 CET using DSA key ID 9480DB97
 |gpg: Can't check signature: public key not found
 |
 |

-- 
x          Þ          ¥          .          O          r          g
GPG-key at http://xdv.org/~jdl/jdl.pub.asc




More information about the Pd-dev mailing list