pattrbackward

the pattrforward object is another highlight, which solves some of my
recent problems to seperate UI objects and other parts of a patch.
Thank you very much and hurray…
Now I want a similar object, which does the reverse. Namely read values
from a named object in the same manner as pvar does this locally.

To explain what I am after a little patch as example, to get values from
a filtergraph~ object. pvar unfortunately is very limited for this kind
of purpose, I can only use one pvar per object, and its restricted to
the local patch.

There are several ways to approach my vision:
One: enhance pattrforward with additional outlets determined by a second
parameter,
or enhance pattrforward with an attribute @backward 1 to let it send the
values of each outlet preceded by a number (or symbol like "out3")
defining the outlet it belongs to,
or create a seperate pattrbackward object which acts like pvar, but with
the possibility to adress objects outside the original patcher,
or enhance pvar to be able to adress objects with the double colon
synthax and allow it to have multiple pvars accessing the same object.

Just if there is some spare time beside doing the big (endian) port ;-),
but let me know what you think.

> or enhance pvar to be able to adress objects with the double colon
> synthax and allow it to have multiple pvars accessing the same object.

I second that request. An object that would bind to all inlets and
outlets of a ui-object specified by a pattr-path and be itself
invisible to pattrstorage, like a all-inclusive send/receive for all
ins and outs. This would be so useful for designing larger interfaces
without creating spaghetti(mikado?)code, having to route patchcords
through multiple subpatches or attaching send/receives to every ui
object.