I have isolated a bug when editing bpatchers in different instances. Example patch included.
Steps to reproduce:
1. Open myMain
2. Click the button to "fill randomly". Each bpatchers will fill their colls randomly, displayed in the referred jit.cellblock.
3. Open any one of the bpatchers to edit. (Contextual menu Object > New View of "myBpatch.maxpat".
4. Allow it to be edited by selecting "Modify Read-Only" in the Edit menu.
5. Edit the bpatchers (even just move something), then save. All bpatch instances should be updated.
6. Click the button to "fill randomly" in any of the other bpatchers. An error message appears in Max window, and it no longer works.
Note that when you now open the original bpatcher, the coll object will still read "#1_myColl", but if you open the coll, it will display "One_myColl" (or whatever instance you saved).
What I think happened:
By saving the edited bpatcher, it saved it as the instance (i.e. One_myColl) instead of the variable (#1_myColl). This becomes clear when you double click on the colls in the non-edited bpatchers, which now have the same name as the edited one (i.e. One_myColl, when it should be Two_myColl).
This makes sense, but what is the point of having "Modify Read-Only" if it makes that instance the default instance?
I've copied the compressed files here, but also attached a zip archive.
Mac OS 10.5.2
MacBook Pro Intel 2.4 Ghz
Save as myMain.maxpat