emvee

After a lot of reading and proofing I still do not understand how I can make use of the pattr system when using several instances of the same abstraction with its named objects, used in the same patcher.

In what way could I make those identical script names unique so I can address them one by one?

The only thing I can think of so far is using an argument in order to create unique names in the instance at load time. However, I suspect there may be a better way.

pattr-and-abstractions

The pattr name is a local one. The names are unique for the parent patcher. As pattr automatically creates unique names for the hosting patcher... 

Name an object, then duplicate it, look at its name...

To access objects in different subpatchers you adress them like:

It's all in the help files and in the docs...

This naming scheme s a strike of genius - thanks to Jeremy for creating it...

The pattr name is a local one. The names are unique for the parent patcher. As pattr automatically creates unique names for the hosting patcher... 
Name an object, then duplicate it, look at its name...

To access objects in different subpatchers you adress them like:
MySub::MyObject,  MySub[1]::MyObject...

Trial and error isn't a bad habit at all. I suggest you to place a pattrstorage into your main patch with several instances of your subpatcher. Then open the client window. The pattr name space will unfold all of its beauty...

You can access each named object with pattrforward directly by the way...

The pattr system is made in a way that you don't need to think about it to much, just throw the objects in. But it does help a lot to understand the principles. Make your own experiments, and try out its behavior. That will teach you more than any written explanation...

If I want to expose UI objects of a subpatcher to pattrstorage, I simply throw in an autopattr and I am done...

Trial and error isn't a bad habit at all. I suggest you to place a pattrstorage into your main patch with several instances of your subpatcher. Then open the client window. The pattr name space will unfold all of its beauty...
You can access each named object with pattrforward directly by the way...
The pattr system is made in a way that you don't need to think about it to much, just throw the objects in. But it does help a lot to understand the principles. Make your own experiments, and try out its behavior. That will teach you more than any written explanation...

Thanks Stefan, your suggestions are very helpful. I 've tried out (a little harder) the different pattr objects to see what they actually can do and how they relate to named and/or UI objects and each other. So now I realize the pattr system is quite powerful and even intuitive (once and only if you get a feel for its basics, that is).

What also needs some trial and error is finding out which (named) objects can be used by which member of the pattr system.

Pattr and Abstractions