I need something like a receive that can dynamically bind to a named object
anywhere in the pattr system. Somewhat like pvar, but global. Any ideas on
how to do this in max/ jscript, even c maybe? Thanks.
Maybe I don't need 1:1 linkage after all, grab will do for now. I still think it would be very nice to have an external like this, to monitor any named object without s/r the way pattrforward can the other way around. Just an idea.
Thanks Jeremy, you're right. I never had a reason before to use the pattr
binding, and I totally forgot about it. I'm always addressing parameters by
sending stuff directly to the specific pattrstorage. I have to rethink my
patch design a little, because I'm scripting modules in different places
depending on the setup, which leads to variable pattr paths, but that's my
problem. The pattr binding is exactly what I need. But it makes me wonder...
what's so special about pattrforward, if you can also use a pattr + bindto
to send a variable to a named object?
Weeeeeeell, kind of. pattrforward allows any old message to be sent
to any named object, not just a message related to the object's
"value", which is what the other pattr objects are concerned with.
the release version will also talk to an arbitrary inlet of the
ah ofcourse:) thanks for your explanation. (last stupid question) The final
pattrforward, will it talk to a named bpatcher's inlets too? pvar and the
current pattrforward don't seem to do that. Or am I missing something
Thijs Koerselman wrote:
> I need something like a receive that can dynamically bind to a named
> object anywhere in the pattr system. Somewhat like pvar, but global. Any
> ideas on how to do this in max/ jscript, even c maybe? Thanks.
Wouldn't this just be [pattr] itself? At least from a parent patcher you
can bind it to subpatcher objects as well.