Re: Quit Command corrupts standalone (stack called by standalone splash)

What about using shutDownRequest? If you don’t pass it, it prevents the quit from happening. Marty > Let me improve this a bit. > > > On 2/23/18 4:19 PM, Phil Davis via use-livecode wrote: >> Roland, >> >> I believe Tom is exactly right. I would restructure your two closing >> handlers like

Re: Quit Command corrupts standalone (stack called by standalone splash)

I save all my stacks on closeTack, that is until I ran into problems with Windows sandboxing in a standalone. I had to conditionally save stacks only if I was in development. Bob S > On Feb 23, 2018, at 15:20 , tbodine via use-livecode > wrote: > > Hi

Re: Quit Command corrupts standalone (stack called by standalone splash)

On 2/27/18 9:40 AM, R.H. via use-livecode wrote: The standalone will start showing strange behaviors especially when the user clicks the standard Windows close button on the upper left corner. That should usually invoke the "closeStack" handler. I'd submit a bug report for this, but as a

Re: Quit Command corrupts standalone (stack called by standalone splash)

Hi Richard and all contributing... Thanks a lot for all answer...))) I have received the corrupted files from clients (original stack that is split into two files during save I guess) and will prepare a bug report attaching them together with the original stack. It is very difficult to know

Re: Quit Command corrupts standalone (stack called by standalone splash)

On February 26, 2018 9:40:58 PM Richard Gaskin via use-livecode wrote: There are many ways that imagined scenario might for all I know be accounted for in the way Dropbox is written. But there may also be other scenarios that can produce the same corrupted

Re: Quit Command corrupts standalone (stack called by standalone splash)

On 02/26/2018 07:38 PM, Richard Gaskin via use-livecode wrote: Consider this scenario with stack files, for example: Mark writes a stack, then I open it, then you open it.  You and I are both making changes, and I save mine a few seconds before you save yours. In that scenario, what's on

Re: Quit Command corrupts standalone (stack called by standalone splash)

Knapp Martin wrote: > Thanks for the in-depth reply. Are there known issues with saving LC > stacks to Dropbox? I was thinking of Roland's issue with corruption > and Phil's suggested fix of watching the file with the tilde character > before allowing a quit to complete. I have an app where

Re: Quit Command corrupts standalone (stack called by standalone splash)

On 02/26/2018 05:14 PM, Richard Gaskin via use-livecode wrote: Knapp Martin wrote: > Richard, could you elaborate on the issues with Dropbox? I first came across it in a search at Google for "dropbox sqlite", looking for tips on making the most of that relationship.  What I found was a long

Re: Quit Command corrupts standalone (stack called by standalone splash)

Thanks for the in-depth reply. Are there known issues with saving LC stacks to Dropbox? I was thinking of Roland's issue with corruption and Phil's suggested fix of watching the file with the tilde character before allowing a quit to complete. I have an app where users create documents (stacks)

Re: Quit Command corrupts standalone (stack called by standalone splash)

Knapp Martin wrote: > Richard, could you elaborate on the issues with Dropbox? I first came across it in a search at Google for "dropbox sqlite", looking for tips on making the most of that relationship. What I found was a long series of support forum and blog posts filled with horror

Re: Quit Command corrupts standalone (stack called by standalone splash)

Richard, could you elaborate on the issues with Dropbox? Is there a recommended procedure for dealing with it? Marty On Feb 26, 2018, at 11:07 AM, Richard Gaskin via use-livecode wrote: > Stack file corruption is very rare with LiveCode. It has happened now

Re: Quit Command corrupts standalone (stack called by standalone splash)

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

Re: Quit Command corrupts standalone (stack called by standalone splash)

Hi Roland, This is the only reply of yours that I see. On 2/26/18 4:13 AM, R.H. via use-livecode wrote: Thanks, Phil and Tom I already replied, but I cannot see my first reply to your answers. Did it appear in the list? Phil: "quitMe" should be sent before 'saveMe' is executed, because

Quit Command corrupts standalone (stack called by standalone splash)

Thanks, Phil and Tom I already replied, but I cannot see my first reply to your answers. Did it appear in the list? Phil: >> "quitMe" should be sent before 'saveMe' is executed, because the 'save' command is blocking. It would prevent 'quitMe' from being sent until (in this case) 1 second

Re: Quit Command corrupts standalone (stack called by standalone splash)

Let me improve this a bit. On 2/23/18 4:19 PM, Phil Davis via use-livecode wrote: Roland, I believe Tom is exactly right. I would restructure your two closing handlers like this: local sMyFilename on closeStack     put the filename of me into sMyFilename     saveMe     send "quitMe" in 1

Re: Quit Command corrupts standalone (stack called by standalone splash)

Roland, I believe Tom is exactly right. I would restructure your two closing handlers like this: local sMyFilename on closeStack     put the filename of me into sMyFilename     saveMe     send "quitMe" in 1 second end closeStack command saveMe    lock cursor /* Tested with and without

Re: Quit Command corrupts standalone (stack called by standalone splash)

Hi Roland. The "~" file is the original (uncorrupted, unsaved) version of your stack before LC executed your Save cmd. If you remove the "~" from the filename, you'll probably find you can open that. LC creates the "~" file at the start of the save operation and, if all goes well, removes that

Quit Command corrupts standalone (stack called by standalone splash)

// Quit Command corrupts standalone (stack called by standalone splash) Using Indy 8.1.9 desktop standalone without encryption (same problem with earlier versions and community version), Windows 7, 8, 10, different machines and different users of a large company. // Before filing a bug report