hello
some notes about the state saving system used by netpd:
the state saving is more a side effect, since the main goal was to provide a system, that makes sure, that all patches have the same state, no matter when a user joins a running session. since that was implemented, it was very easy to use the same system to write states into files and store them again. the netpd-framework only provides functionality to save states of single patches. if you want to save the state of all opened patches, you would need to write your own preset-manager (which is not that difficult and there are already examples). anyway, the netpd-state saving system is made for netpd and does only work for netpd. also i think that other systems like ssad are a bit more straightforward (though i haven't had a deep look into it yet).
supports: -floats -symbols -arbitrary lists -arrays (-and some specialized types more..)
disadvantages:
- is not universal, works only in netpd
roman
On Wed, 2007-02-14 at 14:16 +0100, Luigi Rensinghoff wrote:
Since it is an ever returning subject maybe its good to have a
summarized topic for this.Could someone just give a list of existing "state-saving"-systems and
describe pro's and con's and the state of complexity ?i think that could be very helpful for beginners ;-)
Thanks
Luigi
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de