On Sun, Jan 11, 2009 at 5:01 AM, Chris McCormick chris@mccormick.cx wrote:
On Sat, Jan 10, 2009 at 09:32:32PM -0600, Mike McGonagle wrote:
One thing I noticed is that when you click to open and close these gadgets, it will leave the patch in a "dirty" state, and it will ask you if you want to save the patch before closing it.
Yeah, that sucks for sure, I forgot all about that. Would be great if it was possible to send a message 'clean' to a patch to undo the dirty flag.
Yo, this is definitely a bummer - even for datastructures, populating the data subpatch trips the dirty flag, which is often unwanted when the DS are just transient bits saved via a different mechanism than writing to the patch file (like SSSAD).
But, it seems like a [clean( message might inadvertently cause one to lose work, e.g., if you make a wanted, permanent change, tripping the dirty flag, and then run an operation which sends a [clean( message, you would not be able to distinguish which change was meant to be permanent and which was transient.
So, a different idea might be a message which can temporarily or permanently toggle detection of changes in a patch or subpatch. This way, one could turn off dirty-detection, make a change using [donecanvasdialog(, and turn it back on again. One could then effectively specify which operations are meant to be saved and which are not.
To complete this idea, though, we also need a [savebang] object to fire before the patch is saved to restore the patch to its original state (clearing subpatches, restoring GOP size, etc.). I know this can be built with [tot] but it's not reliable (I have a [savebang] abstraction in sfruit/ which I've tried to use for this purpose - it only works half the time or so).
Best Luke
Chris.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list