Quit Command corrupts standalone (stack called by standalone splash)
martyknappster at gmail.com
Mon Feb 26 17:52:59 EST 2018
Richard, could you elaborate on the issues with Dropbox? Is there a recommended procedure for dealing with it?
On Feb 26, 2018, at 11:07 AM, Richard Gaskin via use-livecode <use-livecode at lists.runrev.com> wrote:
> Stack file corruption is very rare with LiveCode. It has happened now and then, but is rare enough (and of course serious enough) to merit attention by the LC team.
> Even if we can mitigate the issue by altering your code, the main question remains: why does a save operation become interrupted, and is that interruption caused by external factors or from an internal bug?
> Unless you know the cause of the corruption (failing hard drive, flaky network with mounted network drive, use of Dropbox or other synced folder with unpredictable behavior, etc.) it may be helpful opening a bug report if only to allow the team to investigate the corrupted file to see if it brings their attention to something internal which may need refinement.
> Richard Gaskin
> Fourth World Systems
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode