HI, in extension to my previous post about dynamically creating toggle objects:

http://puredata.hurleur.com/sujet-1618-problems-creating-objects-dynamically

I have been doing this successfully, so I decided to wrap it up as an abstraction and $0 everything, so as to have multiple instances - things like this are useful

THe problem is that I'm having trouble referencing the abstraction on the root level (i.e 'this') and creating the toggles when the abstracton is created as [myAbstraction $0] (with a unique ID)....well this is tricky to explain:

If I reference a subpatch [pd $0-toggleSubPatch] to create the toggles inside it works fine. I can graph on parent them and its fine. It just seems a bit clumsy having to reference a child to create the toggles inside, rather than reference the parent patch to create the toggles on the same level

I guess I'm having the problem of parsing an ID string to the message box correctly:

Is [abstraction $0] the same as [pd $0-abstraction]? (1123-abstraction for example)

does this make sense? - I have a cold and its really hard to explain :/

>>
Is [abstraction $0] the same as [pd $0-abstraction]? (1123-abstraction for example)<<

NO...it is not the same.

to explain what happens if you create [abstraction $0] :

if you create [abstraction n]....then the first argument for this abstraction is going to be n. the way to get that first argument is by typing ' $1 ' into an object... so, for example, an object called [select $1] inside an abstraction called [abstraction 187] will actual be equal to [select 187]

in this case, the $0 will have no impact on the NAME of the abstraction...but rather, the unique $0 value given to each instance of that abstraction will be translated into a $1 value for each object inside each abstraction.

in your second case, [pd $0-abstraction], the $0 value is given directly to the NAME of the subpatch. so the only thing that the $0 value will affect is the receive name for the subpatch when you want to send dynamic information to it.

after reading and re-reading your post, i think what you are asking for is a way to make sure that dynamic information is only passed on to individual instances of abstractions which all share the same name....which i unfortunately have a feeling is impossible. you cannot name your abstractions [$0-abstraction] , and [abstraction $0] is not the same as [pd $0-abstraction].

i think your only option is to use subpatches and graph on parent.

someone might have an idea, but i just sat here for 15 minutes thinking about it and i really think that if you have two abstractions both named [bob] , then the only way to dynamically create objects is to send the info to [bob] ...in which cases both [bob]'s are going to receive the info to create objects..which isn't what u want.

i really think you have no choice but to create subpatches

Thats cool I dont mind using the extra subpatch if thats the way to do it. I have this (unhealthy) obsession with doing things properly!

thanks for the clarification

S