Hallo, patco hat gesagt: // patco wrote:
Well, we could also use an array and check in properties "save content" Or we could use two messages boxes [set $1(---[ ( and a loadbang (like in the little bagoftricks memory) Or we could use the object [init] with using the second inlet for setting the memorized value, ect...
I would really recommend to take a look at [sssad]: For a simple general purpose state saving it is much more flexible than the solutions above and still only uses builtin objects (with pd 0.39).
if you use various [textfile]s to do the actual state management with sssad or if you wouldn't mind to access the harddisk with preset-switching it even allows storing different presets, not just a "snapshot" of the current state of things, which is the original motivation of [sssad]. I attached a little example how to do this.
But if we need to store several lists of parameters, that could become very complicated, Anyway, the last patch submitted fits very well the patch I am experimenting that needs a little memory,
Here I would recommend to use a [textfile] instead of the message box. It's quicker than changing the message box all the time, and the messages to [textfile] are very similar to those you send to a message box.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__