Here's something getting in the way and I'm not I'm dealing with it the best way:
What I'm coming up against here is how to manage subpatchers & abstractions. In my case, a need large numbers of instances of the same abstraction in the main patch. But I also need a few elements at various levels in each instance to be 'customized' or specific to that instance. Seemed like the way to do this was to open the instance, make the specific change to it, and say *don't save* to leave the original intact. So then I have this customized instance that's now 'disconnected' from any further changes made to the original.
So in trying to develop the patch, when I make a change to the basic content of the original abstraction, I end up having to go back and re-doing all this work...Putting in new instances of the updated abstraction, going into each and changing the various things that need to be customized, re-patching, etc.
Is there a better way to handle this, or is it just what we have to live with in this case? I've done things like use as few as I can when developing, and trying to do an "initialize" routine where I send as many customizations as I can to the instances as variables. This works OK some of the time, but has it's own side-effects.
Just wondering if this is the best track, or there is a better one that hasn't dawned on me yet?