Hi,
sorry for coming in late to this thread - I'm currently forced to stay away from my desk for some days ...
Regarding "u_dispatch $0 symbol": Because of the [list trim] that is applied to all incoming parameters, it would never filter any data. [u_dispatch] is like a simplified [route] that doesn't make a difference between "list frequency 440" and "frequency 440", so you can send it either kind of message and don't have to fiddle with [list] or [list trim] on your own. In my experience, this has been easier for users, who are not so familiar with Pd's message type system and its pitfalls.
You can easily work around dispatching symbol-messages by using different selectors. To set a table name for example, I'd use [u_dispatch $0 tablename]. The only issue then is that [u_dispatch] doesn't generate full symbol-messages, instead it generates "meta-messages" without symbol-selector.
This:
[mytable(
|
| [symbol mytable(
|/
[u_dispatch $0 tablename]
will send a "mytable"-message to [r $0-tablename] for both messages (because of the [list trim] "symbol mytable" gets converted to "mytable").
To get a "symbol mytable" message again, use [symbol] or [list]. To feed it into a messagebox with $1 or so inside, add a [list] in front.
Hint: You can save yourself many headaches if you *always* put a [list] in front of any message box with dollarsigns!
Now regarding the poly objects in rj library: [u_makepoly] is geared towards making midi-like instruments polyphonic. For granular approaches, it maybe is better to use the more simple [u_robinpoly]: It schedules the created objects in a round robin fashion and will accept any kind of trigger message, not only midi-like note/velocity pairs.
If you need more control and want to access specific instances directly, there is no object for this in the rj library (yet), but Hans did some poly objects that allow this, or use the old nqpoly or so.
Ciao
Frank
On Fri, Mar 11, 2011 at 09:08:05AM -0500, Peter Kirn wrote:
On Fri, Mar 11, 2011 at 5:18 AM, Joe White white.joe4@gmail.com wrote:
P.s. We're in the process of creating some online documentation (similar to Max) for all the objects in the library. It'd be great to get some feedback once it's finished.
Hi Joe, No, I found the problem -- the issue is that the u_dispatch abstraction doesn't work with symbols. If I'd looked closely at the help file, I would have noticed the prominent comment to that effect. ;)
This actually turns out to be a fairly significant issue, because I'd ideally like to pass different arrays into the abstraction. Suggestions?
Maybe there's another way to pass in the symbol for the array, like multiplexing as an argument on instantiating those patchers?
Or maybe u_dispatch $0 symbol is fixable?
(And yes, I'm happy to have a look at the documentation, or even contribute prior to it being completely finished ... editing is kinda one of the things I do, and it's the least I can do to give back to this amazing library!)
Peter
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list