zarby

if i modify a coll embedded in a patcher is it normal that the dirty flag is not set?

How to save a patcher and all the embedded things?

if i modify a coll embedded in a patcher is it normal that the dirty flag is not set?
How to save a patcher and all the embedded things?

how-to-save-patcher

Yes, Zarby, the coll data is saved as another file, and not part of the patch, so it doesn't affect the patch dirty flag. maybe you could set it manually whenever you change the patch, but I stopped using the coll object for that very reason and use pattrstorage instead, which does set the dirty flag, and also I preferred pattrstorage because it easier to have multiple objects with different collections, no external files to maintain. so I don't know how to set dirty manually. Or you could switch to using pattrstorage like me :)

If you're interested in trying pattrstorage, start by looking at the pattr help page, it shows how to store collections in a pattr object

yes i already use pattrstorage for another more complicated file,

but i want to use embedded coll for a simple file and i want to know how to save it!!!!

yes i already use pattrstorage for another more complicated file,
but i want to use embedded coll for a simple file and i want to know how to save it!!!!


If you want to save the data inside coll, you can save it in an external file using write messages, then use read messages to load the data triggered by a loadbang, but you don't need to do the read messages explicitly if the data file has the same name as the coll and is in the same directory as the patch. If it finds a file of the same name when starting up, it tries to load the data transparently.

After you load the data, a coll can reference data from another coll, but it still doesn't save inside the patch itself. See the access tab in the coll help file for examples.

If you want to save the data inside coll, you can save it in an external file using write messages, then use read messages to load the data triggered by a loadbang, but you don't need to do the read messages explicitly if the data file has the same name as the coll and is in the same directory as the patch. If it finds a file of the same name when starting up, it tries to load the data transparently. 

After you load the data, a coll can reference data from another coll, but it still doesn't save inside the patch itself. See the access tab in the coll help file for examples.


thank you, you try to find a solution but i think the best way to improve max is to fix the bug

How to save patcher?