I'm finding the potential for some confusion when dealing with multiple copies of abstractions that get added and editing over different points of patch development.
Just to verify what I found by trying it:
1. If I edit an abstraction in a patch with CMD+double click and save changes, the stand-alone abstraction on the disk is modified (i.e. the Max patch that is the abstraction). This affects any NEW instances of that abstraction in patches, but not previous ones.
2. If I edit and don't save changes, the edits stick for that instance of the abstraction, but nothing else, and the patch file is not modified.
3. If I duplicate any existing instance (CMD+D), the 'duplicate' is the current patch file at that time-- which is not neccesarily a literal duplicate of the abstraction I ran the duplicate command on (due to #2).
Question #1: So is there a way to create a bunch of instances and 'link' them to the abstraction file so that they all change when it changes?
Question #2: This all seems a bit confusing and like it could create some headaches over the course of developing some larger. Are there any suggestions/workflows/rules for keeping it all straight? Or is it somehow much simpler and I'm missing it?