Close Stack Cleanup

[Bob Sneidar]

Thanks Curry. That works for the IDE, but not for the standalone. End Users do not save their stacks, as I give them no way to do so. The stacks in my app perform two functions: An interface to control the app and also a place to store persistent data i.e. properties. If a user force-quits my app for any reason, saving upon closing a sub stack ensures those updated properties are retained.

I could test for the IDE I know, but for my purposes, having lost so much form modifications in the past due to some kind of race condition or IDE lock up, I auto-save regularly, not just when I close a stack.

As an aside, this is what was slowing my Windows Standalones down so much. It has been well documented that the performance of saving a stack (especially one as complex as mine) in Windows is fairly oppressive. In a Windows Standalone I have to trap most of the times I save a stack, allowing only for saving upon close.

Bob S


On Feb 4, 2021, at 3:17 PM, Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:

Me again:

Don't think "clean up and save." Keep the twain separate.
I choose when to save, it's a conscious choice, and it fires my cleanup.
My stack is almost always saved clean.