Hey all,
I missed this reference.
Anyhow as for pixelTANGO when you mess with the patch structure you break the names. So the user has to:
a. close the patch and reopen it after the change b. send a magic message to update the "tags" (This is not yet implimented)
so I have not found any brilliant solution to the issue.
Note in pixelTANGO I'm only concerned with abstractions in each chain, so that "tags" are generated based on the abstractions position in the chain, assuming everything is flat... (no nesting) I have also not resolved issues with chains that split... (one video on multiple objects).
.b.
Frank Barknecht wrote:
Hallo, geiger hat gesagt: // geiger wrote:
One could generate the ID automatically based on the name of the abstraction, its position (relative to the other abstraction with the same name) and the ID of the parent patch.
This way it might be possible to come up with unique ID's without having to name your abstractions individually.
e.g
MAIN1/abs4/subabs3
would be the 3rd abstraction "subabs" (ordered with increasing x then y) in the 4th abstraction "abs" in the main patch "MAIN".
I thought of that as well, but how do you deal with edits of a patch? Say you delete or recreate an abstraction instance, how should Pd know which abstraction is used for which saved data? Maybe Ben Bogart can say something about how he did it in picelTANGO, where auto-generated "tags" are in use as far as I understand.
Ciao