Autosaving stacks corrupted on network drives

[Trevor DeVore]

On Tue, Oct 24, 2017 at 6:03 PM Mike Kerner via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Yes, this especially happens with simultaneous sync tools such as google
> drive (now backup and sync), microsoft ,oneDrive box, and dropbox.  There
> are a variety of things that play into this annoying behavior, but the most
> common one is timing and latency/connectivity.  It really gets to be bad if
> you  quit/save from one machine, and then fire it up from another before
> the sync/save is complete.


I’ve seen similar problems as well. Another option would be to save the
file to the temp folder and, if that operation is successful, delete the
original file and move the file from the temp folder to the correct
location.

Trevor DeVore