ok, i was a little confused by your UI change at first, but reading your reasoning, it makes a lot of sense. the fact that you can override the safe behavior with both a message and a keystroke is awsome and removed any objections i had. thanks.
-josh
Miller Puckette wrote:
Well, there are two problems... first, in a performance you'd sure like some way to avoid closing patches by accident, even if they're clean.
Second, it's possible to make a long audio recording into an array (for example) without making the patch know it's "dirty".I think the proper default behavior is the most careful one (the way it is now), but am not sure how to allow or encourage the user to override this, whether it should be selectively for individual patches, or as a global override, or even some combination of both.
cheers Miller
How about if there is anything to 'Undo' in the Edit menu, the user is asked if they want to save the changes?
Martin
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list