#0-naming of abstractions
I'm struggling a bit with the #0-system for automatic identification of multiple instances of a subpatcher. I finally managed to get it to work for the buffers in the abstraction, but I how do I get it to work with the actual abstractions? I'm creating a library of modules with snippets of bpatchers and I'd rather not have to name each instance manually.
#0 alone will help to individualize multiply copys of the abstraction, but you will not automatically know what #0 will turn into, which can be required when you watn to work the patcehrs with the outer world.
what would be your exact aim or scenario?
Ok, so I got it to work now - by writing [bpatcher buffertest #0]. Since I have a snippet with the bpatcher, I would like to be able to apply #0 to the bpatcher in some other way. If I write it as an argument in the inspector the new instances don't seem to get an individual name/number.
But I can of course also remake the snippet.
depending on the context it will work fine to either script-create the bpatcher including its arguments or write the arguments one by one in the inspector of the bpatcher.
normally when you change arguments on an object the object (including the bpatcher object) should be re-loaded and therefore reflect the changes you´ve applied.
there might be a solution for dynamic arguments (auch as cunting 1,2,3... ) for snippets or protoypes, too, but then i dont know it. as long as you want always the same argument (#0) a copy of the snippet in question is probably all you need.
in case you dont do it already, for buffer & co i would recommend to use [buffer #0_customname], using a plain 4 digit number as unique name for something can get confusing sooner or later.
