self-modifying abstractions

[pix]

another self reply... sorry for making so much noise on the list while i
talk to myself. but anyhow, i worked out how to accomplish what i want
(which is a little hard to explain right now), but i realised that by
manually editing the name of an object in the .pd file to be (for example)
"\$1", then you can change the name of that object using a parameter to
the abstraction (as long as it has the same configuration of in's and
out's). with some craftily designed sub-abstractions you can use this to
reconfigure the abstraction at creation time.

pix.

On Tue, 25 Sep 2001 11:53:40 +0200
pix <pix at test.at> wrote:

> wow, i just found myself asking almost the same question earlier this
> year, on this list *slap*.
> 
> okay, so miller writes:
> > If you name a subpatch "fred" for instance, you can send messages to 
> > "pd-fred". I've used it to add text comments to windows automatically,
> > but in principle you should be able to do anything that appears in a
> saved 
> > Pd file (adding and connecting objects). 
> 
> the problem here is that if you have two abstractions called fred, the
> actions appear to happen to both of them (i've just been playing with
> the
> selectall at the moment), which makes it a little less useful than i had
> first imagined.
> 
> is this something that can be avoided?
> 
> pix.
> 
> On Tue, 25 Sep 2001 11:45:44 +0200
> pix <pix at test.at> wrote:
> 
> > hi there,
> > 
> > because there is no real documentation on this 'hack' i thought i'd
> > query
> > the pd-list hive-mind first:
> > 
> > regarding the self modifying patches (sending messages to pd-blah.pd
> > etc),
> > is it possible for an abstraction to reference itself somehow? what is
> > the
> > name of the object that you send the messages to?
> > 
> > my real query is, can an abstraction 'reconfigure itself' based on a
> > parameter supplied at creation time?
> > 
> > pix.