Re: LC puts stuff in the trash upon quit!

Thanks for getting back to me on this. This bug has been around for over 3 years now. Will it ever get squashed? Rick > On May 15, 2021, at 12:06 PM, matthias rebbe via use-livecode > wrote: > > There is a bug report for this already > > https://quality.livecode.com/show_bug.cgi?id=21233 >

Re: LC puts stuff in the trash upon quit!

There is a bug report for this already https://quality.livecode.com/show_bug.cgi?id=21233 > Am 15.05.2021 um 15:46 schrieb Rick Harrison via use-livecode > : > > I have noticed this oddity for a long time. > No other program that I own does this. > > Why is LC so dirty? > > Rick > >

Re: LC puts stuff in the trash upon quit!

Hi Rick, > Am 15.05.2021 um 15:46 schrieb Rick Harrison via use-livecode > : > > I have noticed this oddity for a long time. > No other program that I own does this. this is a known bug: > Why is LC so dirty? Must have to do with cheese...

Re: LC puts stuff in the trash upon quit!

On which operating system is this? I have not noticed it on MacOS or Xubuntu Linux. Richmond. On 15.05.21 16:46, Rick Harrison via use-livecode wrote: I have noticed this oddity for a long time. No other program that I own does this. Why is LC so dirty? Rick

LC puts stuff in the trash upon quit!

I have noticed this oddity for a long time. No other program that I own does this. Why is LC so dirty? Rick ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription

Re: launch & quit

Robert: > Have you tried to switch off messages before quit? Yes - get angry and then quit with prejudice. Lock messages, unload libraries, close stacks, etc, and really QUIT! :) Also, consider an alternate approach to launching the second app, so that shell doesn't keep your first

Re: launch & quit

I’d guess that quit command triggers some closeXxxx handlers to run and one causes the delay. The duration of delay sounds a bit like network timeout. Have you tried to switch off messages before quit? On Oct 12, 2019, at 13:28, Paul Dupuis via use-livecode wrote: I have a stand alone

Re: launch & quit

I’ve used quit before on Mac with no problems, so I tried a few tests and it still seems to work fine for me (even with your mismatch variable tError/tErrormEssage). I tried both with and without generating a deliberate error and it quit straight away, so I’d guess there may be something else

launch & quit

  if tError is not empty then     answer error tErrormEssage   end if   quit end mouseUp On Windows, the designated application launches promptly and my app quits immediately. On OSX, the designated application launches promptly and my app waits way too long (a minute or two) before quitting

Re: The correct way to quit a Windows standalone

If you look at the script i posted before, then you see for windows /T and /F and so on. This will kill the application and all child processes. On 23-05-19 17:59, Bob Sneidar via use-livecode wrote: So this seems odd to me. If an executable that spawns other processes/threads (if that is

Re: The correct way to quit a Windows standalone

So this seems odd to me. If an executable that spawns other processes/threads (if that is what a splash stack is doing) quits, Windows should also terminate the processes/threads. I suppose, from reading various email posts here that there are different ways to implement a splash screen. As I

Re: The correct way to quit a Windows standalone

Actually, this all seems like a Windows "bug" to me. A language like LiveCode, should, if I script 'quit', do exactly that - quit. If there are any open anythings preventing that, the engine should shut them all down for us. Now as a software developer, I agree that good programmin

Re: The correct way to quit a Windows standalone

://www.hyperactivesw.com On May 23, 2019 8:14:59 AM Paul Dupuis via use-livecode wrote: If it is a requirement for any loaded fonts to be unloaded from memory for a Standalone to actually quit under Microsoft Windows then a bug should be entered at https://quality.livecode.com/ to update the Dictionary entries

Re: The correct way to quit a Windows standalone

If it is a requirement for any loaded fonts to be unloaded from memory for a Standalone to actually quit under Microsoft Windows then a bug should be entered at https://quality.livecode.com/ to update the Dictionary entries for: closeStackRequest shutDownRequest quit start using font stop

Re: The correct way to quit a Windows standalone

quote & tPath & "/TrajanPro-Bold.otf" & quote into tTrajanProBold stop using font file tTrajanProRegular stop using font file tTrajanProBold close this stack quit end closeStackRequest ~Roger ___ use-livecode mailing l

Re: The correct way to quit a Windows standalone

i use this which works ok on windows but hangs on Macos(when clicking the red x, it works when going to quit via the menu, i don't know why) if the environment is "standalone application" then   if the platform is "Win32" then --added /T and /F, /T Terminates p

Re: The correct way to quit a Windows standalone

NVM Apparently I am supposed to use lock messages to force a quit. There may be something in my code that is halting the quit process, but I don't really need to do any housekeeping, so this works. Bob S > On May 17, 2019, at 13:37 , Richmond via use-livecode > wrote: > > As

Re: The correct way to quit a Windows standalone

Need a speel chekr. I meant to say, "...but it doesn't quit. It tosses an error and the processes continues to run. Bob S > On May 17, 2019, at 13:43 , Bob Sneidar via use-livecode > wrote: > > but it doesn't wuit it tosses an error and the precess

Re: The correct way to quit a Windows standalone

. Yes I do hide the splash stack, not sure why someone wouldn't. When I quit, I am quitting the actual Splash application, but it doesn't wuit it tosses an error and the precess continues to run. I will have to poke around somehow to figure out why. Curious, the Apple standalone does not behave

Re: The correct way to quit a Windows standalone

h stach in a Windows Standalone. When I close (or otherwise quit) the stack which the splash stack opens (the actual application) I get a runtime error, and the Splash process continues to run. What is the proper way to cleanly exit an app of this nature? Bob S ___

The correct way to quit a Windows standalone

Hi all. I have a splash stach in a Windows Standalone. When I close (or otherwise quit) the stack which the splash stack opens (the actual application) I get a runtime error, and the Splash process continues to run. What is the proper way to cleanly exit an app of this nature? Bob S

Re: Quit an Android

The user isn't asking for a way to quit, just for a controlled exit. Typically this is done from the entry screen (the Home stack in this case) when the Back button is pressed. Right now the app says "you are home" and blocks the backKey message. Instead, ask if they want to quit

Re: Quit an Android

Sannyasin Brahmanathaswami wrote: > I have two requests that there be way to quit the app. Few apps have that. Why do those users want this? > I may not have got that right… or maybe there are nuances about the > way Android works. Can you remind to Best Practice? Mobile OSes prese

Quit an Android

Yay! The SivaSiva app works well on Android. 1 ½ years in the making! I have two requests that there be way to quit the app. But I recall you telling me that "User knows how to quit." And that "quit" was not an important function in the app itself. I may not have got

Re: Android won't quit

There's a pull request already, Panos was on it immediately. It will be fixed in the next release. Apparently the problem was reintroduced accidentally after it was fixed the first time. Android has a swipe-to-kill also but a clean quit is better, of course. I do understand about

Re: Android won't quit

Well, thanks Ralph snaky explanation, I am gonna opt out. Call it a feature "will not implement" and tell beta testers "This goes against Android OS. If want quit the app, use the Android "Force Quit" Even on iOS they have double click home and swipe up Jac

RE: Android won't quit

: This is not an easy thing to fix and can be broken easily. The app in memory is not corrupt but the restart of the app is probably exposing an LC engine bug. Details for geeks... To handle the Android unique app restart protocol: After you "Quit" or the app gets hibernated so to speak

Re: Android won't quit

When I first reported it, the problem was that the quit command unloaded all the libraries but left the app in memory. Sounds like what you see now. In my app it just crashes, but probably for the same reason. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http

RE: Android won't quit

This is not an easy thing to fix and can be broken easily. The app in memory is not corrupt but the restart of the app is probably exposing an LC engine bug. Details for geeks... To handle the Android unique app restart protocol: After you "Quit" or the app gets hibernated s

Re: Android won't quit

Argh. I thought I solved in this in my app. But LO... it appears to quit... but is actually not quitting... it leaves a "corrupt" stack on the phone (android) and when you try to restart it, it opens to splash screen stack, but no messages are firing. It is "stuck" ; doe

Android won't quit

Does anyone have a workaround to completely quit an Android app? I just re-opened this bug report that claimed to have fixed the problem but it didn't really: https://quality.livecode.com/show_bug.cgi?id=19420 I can block the backKey message and do nothing, but then the user can't use

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

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

start > of the save operation and, if all goes well, removes that file when save is > complete. > > My guess is your problem is rooted in the lengthy save time in the quit > routine. Here are a couple ideas of how you could deal with that: > > 1) Do the save within a try/catch statem

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)

. That should usually invoke the "closeStack" handler. Using my own "Quit" menu seems to be safer. Using try and catch and various ways of quitting and saving did not make any difference. The error message using "catch" in the "try" statement should have been wr

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

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)

d, because the 'save' command is blocking. It would prevent 'quitMe' from being sent until (in this case) 1 second after 'saveMe' has finished. Well, it is blocking. Issuing "quit" just quits if messages are locked.So, to quit before save would require not to force a quit. Right? I will

Quit Command corrupts standalone (stack called by standalone splash)

s case) 1 second after 'saveMe' has finished. Well, it is blocking. Issuing "quit" just quits if messages are locked.So, to quit before save would require not to force a quit. Right? I will test. The main problem is that the IDE is ok, even though saving takes a long time, but no errors

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

d quitMe    if there is a file sMyFilename then   unlock cursor   lock messages   quit    else   send "quitMe" to me in 0.5 seconds -- or in your preferred time    end if end quitMe The above was not tested but it should solve the problem. HTH - Phil Davis On 2/23/18

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

nd without locking and showing cursor */    set the cursor to watch    save this stack /* auto save, takes a long time, between 10-30 secs */ end saveMe command quitMe    if there is a file sMyFilename then   unlock cursor   lock messages   quit    else   send "quitMe"

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

and, if all goes well, removes that file when save is complete. My guess is your problem is rooted in the lengthy save time in the quit routine. Here are a couple ideas of how you could deal with that: 1) Do the save within a try/catch statement so you can deal with any error. 2) If you are just sa

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

Help needed / corrupted application stack after quit through splash stack

iled error report for such standalone. I have a friend who experiences this problem each time, and each time he wants to use my app, he then takes a fresh copy that is good only for a 1-time-usage ))). The quit command is sent from the application stack. Here are the handlers in the applica

Re: LIvecode quit unexpectedly errors.

I've had the same problem with 9.0dp6, unexpected crashes, sometimes a whole string of them, also not reliably or reproducably or predictably. It may be just coincidence, but when I told the firewall to deny LC it seemed to get a little better. (I'm still getting asked about remote access on

Re: LIvecode quit unexpectedly errors.

On 04/05/2017 01:27, Jonathan Lynch via use-livecode wrote: Is it a new installation? No, it's 9.0.0DP6 which I've had installed and in use for a while. It's a new-ish stack that I'm having trouble with - but sadly not reliably or reproducably or even vaguely predictably. I'll send in a

Re: LIvecode quit unexpectedly errors.

If you are getting a crash on Mac then including the crash log is very helpful as we can symbolicate them and often see exactly where the crash is. A reliable recipe (preferably a stack that causes the crash) so we can replicate it under a debugger is also a huge help. Often without one or both

Re: LIvecode quit unexpectedly errors.

Is it a new installation? Sent from my iPhone > On May 3, 2017, at 8:10 PM, Alex Tweedly via use-livecode > wrote: > > > Sorry, I should know this but I guess I've been very lucky so far :-) > > I have just started (first time in 12 years or so of using

LIvecode quit unexpectedly errors.

Sorry, I should know this but I guess I've been very lucky so far :-) I have just started (first time in 12 years or so of using LC/Rev) getting crashes. How do I report these ? Obviously, open a bug in QCC - but what file(s) do I need to include to help find the problem ? Thanks

Re: How to quit an Android app

On 23/12/2016 3:46 AM, Richard Gaskin wrote: J. Landman Gay wrote: > I did write about it but I hadn't tried it yet. You were right on > the nose, that fixes it. I had to allow a short wait. This fails > as before: > >tsNetClose >quit > > But this works: >

RE: How to quit an Android app

I just had an interesting Android quit issues. I have to check if this is an Android problem only or a characteristic of the base engine. I wonder if this is related to stopping the debugger in the IDE and have some calling handler do something? Command test1 Repeat while not test2() Answer

Re: How to quit an Android app

Point taken. However, being an IT person and having to work with customers to resolve their issues, I find that regularly, the user will miss some critical piece of information that would take me right to the problem. Not only that, I have found that more times than I would like to admit, the

Re: How to quit an Android app

To be fair, a test stack isn't always required. They're actually pretty flexible about that. What I meant in my post was that if the test does, in fact, need a stack in order to adequately report it, I tend to procrastinate because I'm almost always in the middle of something else. If there's

Re: How to quit an Android app

IMO, having a *requirement* for a user to create a test stack - EVEN IF THE SIMPLE DESCRIPTION IS CLEAR AND UNAMBIGUOUS - is an unacceptable bureaucratic nonsense. I'm all in favour of creating test stacks to demonstrate a problem - esp. if the originally failing stack is complex, or if this

Re: How to quit an Android app

On 12/22/16 11:46 AM, Richard Gaskin wrote: I would like to think that the introduction of the new external would not require us to rewrite our apps. Have you filed a bug report on that? No, for a couple of reasons. First, it doesn't seem much different than the need to close all running

Re: How to quit an Android app

J. Landman Gay wrote: > I did write about it but I hadn't tried it yet. You were right on > the nose, that fixes it. I had to allow a short wait. This fails > as before: > >tsNetClose >quit > > But this works: > >tsNetClose > wait 1 with messages &

Re: How to quit an Android app

I did write about it but I hadn't tried it yet. You were right on the nose, that fixes it. I had to allow a short wait. This fails as before: tsNetClose quit But this works: tsNetClose wait 1 with messages quit Success! :) On 12/21/16 11:17 AM, Matthias Rebbe wrote: Hi, ignore

Re: How to quit an Android app

but did you try tsNetClose before quitting. This > would close all open connections and disables tsNet. > > Matthias > > >> Am 21.12.2016 um 07:24 schrieb J. Landman Gay <jac...@hyperactivesw.com >> <mailto:jac...@hyperactivesw.com>>: >> >>

Re: How to quit an Android app

Hi, just a shot in the dark, but did you try tsNetClose before quitting. This would close all open connections and disables tsNet. Matthias > Am 21.12.2016 um 07:24 schrieb J. Landman Gay <jac...@hyperactivesw.com>: > > Sending "quit" in 10 milliseconds doesn't crash

Re: How to quit an Android app

Sending "quit" in 10 milliseconds doesn't crash the app on second launch (good.) But it hangs for a while and then returns a "socket timeout" message. So it does look like maybe it's TSNet. On 12/21/16 12:20 AM, J. Landman Gay wrote: Yeah, I tried that. Maybe "in 0

Re: How to quit an Android app

t from RAM, I'll look it up and see if that's the problem. I assume no one else sees this? On 12/20/16 11:40 PM, Scott Rossi wrote: Maybe try sending the quit command after a short delay instead of from within the handler? Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design

Re: How to quit an Android app

Maybe try sending the quit command after a short delay instead of from within the handler? Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 12/20/16, 9:38 PM, "use-livecode on behalf of J. Landman Gay" <use-livecode-boun...@lists.runrev.com on

How to quit an Android app

I have an Android app with a simple handler: on doQuit quit end doQuit It quits as directed. On relaunch it crashes. On a second relaunch it works fine. This is consistent behavior. I have tried sending "quit" in 0, locking messages, etc. How do you cleanly quit an Android

RE: Forcing an android app to quit when the 'home' button is clicked?

to quit when the 'home' button is clicked? Terry, Reading the docs, I'd say the following should be possible: on backKey quit end backKey Kind regards, Mark Schonewille http://economy-x-talk.com https://www.facebook.com/marksch Buy the most extensive book on the LiveCode language: http

Re: Forcing an android app to quit when the 'home' button is clicked?

>Sent: Monday, January 18, 2016 7:46 PM >To: How to use LiveCode >Subject: Re: Forcing an android app to quit when the 'home' button is >clicked? > >Terry, > >Reading the docs, I'd say the following should be possible: > >on backKey > quit >end backKey > >Kind

Re: Forcing an android app to quit when the 'home' button is clicked?

tdown" message which is sent when you issue the "quit" command, but that doesn't happen when the Home key is pressed because the app doesn't quit, it keeps running in the background until Android needs the memory. The app should save its state on every significant change because

Re: Forcing an android app to quit when the 'home' button is clicked?

Thanks Jacquie - you’re right, suspendStack doesn’t seem to be supported by either iOS or Android so no joy there. I wanted the app to quit when the user navigated away from it because I have a routine that attempts to sync files that have been saved but not uploaded each time the app starts up

Forcing an android app to quit when the 'home' button is clicked?

On iOS the fact that a LC app routinely quits when the home button is clicked can be a pain but in the case of the app I’m currently developing I actually want this to occur. Anyway, I’m covered on iOS but how do I make the app quit when the user leaves it on an android device

Re: 'Quit' mystery

In my case, my second stack *was* a substack and quit still didn't work. On Wed, Nov 11, 2015 at 9:42 PM, J. Landman Gay <jac...@hyperactivesw.com> wrote: > That's what I suspected; the stacks aren't actually substacks. Now it > makes sense. Thanks for the clarification. > > O

Re: 'Quit' mystery

t in the main? >> > > Yes, that's how it should work. I've been wondering why the extra handlers > in substacks were required, I've never needed to do that and my apps have > always quit. I'd say go with the simpler solution and if that doesn't work > then we can figure out wh

Re: 'Quit' mystery

ack be passed up the message path to the main stack? In which case you don't need shutdownRequests in each sub, just in the main? Yes, that's how it should work. I've been wondering why the extra handlers in substacks were required, I've never needed to do that and my apps have always quit. I'd say go

Re: 'Quit' mystery

ts in each sub, just in the main? Yes, that's how it should work. I've been wondering why the extra handlers in substacks were required, I've never needed to do that and my apps have always quit. I'd say go with the simpler solution and if that doesn't work then we can figure out why. --

Re: 'Quit' mystery

card of the main stack. >> >> substack stack script >> --- >> on shutdownRequest >>send "preparetoquit" to card "main" of stack "mainstack" >> end shutdownRequest >> -- >> The main card of th

Re: 'Quit' mystery

couldn't get my standalone to > quit no matter what. This did the trick. > > On Tue, Nov 26, 2013 at 10:19 AM, Martin Koob <mk...@rogers.com> wrote: > >> Hi >> >> It has been a long time since I set this up in my application so I don't >> remember

Re: 'Quit' mystery

probably it has not been fixed yet. > All the best, > Paolo > > On Thu, Nov 5, 2015 at 4:47 AM, Howard Bornstein <bornst...@designeq.com> > wrote: > > This really helped me out. Thanks Martin! I couldn't get my standalone to > > quit no matter what. This did the trick.

Re: 'Quit' mystery

This really helped me out. Thanks Martin! I couldn't get my standalone to quit no matter what. This did the trick. On Tue, Nov 26, 2013 at 10:19 AM, Martin Koob <mk...@rogers.com> wrote: > Hi > > It has been a long time since I set this up in my application so I don't >

Re: Standalones requiring force-quit (and messages?)

Only time I have to force quit is if I made a database call to a stale database connection, and that of course is my fault for not closing the connection when done with it. About the only way to find something like this is to have a logging system that records everything your application does

Re: Standalones requiring force-quit (and messages?)

On 2/27/2015 11:56 AM, Dr. Hawkins wrote: There isn't any code that should be intercepting the quit or shutdown requests, but I'm wondering if the period handlers could be somehow blocking this? e.g., ones like on doIt doSomething send doIt to me in 100 milliseconds end doIt This means

Standalones requiring force-quit (and messages?)

I've been force-quitting the IDE as my standard so long that I don't give it any thought . . . the frequency with which it gets lost, beachballs, or whatever is high enough that I usually don't even try a plain quit. Anyway, as I'm being advised that the standalones that people are testing

Re: Standalones requiring force-quit (and messages?)

On 27/02/2015 17:56, Dr. Hawkins wrote: I've been force-quitting the IDE as my standard so long that I don't give it any thought . . . the frequency with which it gets lost, beachballs, or whatever is high enough that I usually don't even try a plain quit. Something isn't right on your set-up

Re: Standalones requiring force-quit (and messages?)

is empty cancel item 1 of line 1 of the pendingMessages end repeat end closeStack Paul -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Standalones-requiring-force-quit-and-messages-tp4689450p4689468.html Sent from the Revolution - User mailing list archive

Re: How to Quit with a button

Are you saying locking messages before quitting prevents the Save dialog from presenting? I didn’t know that. Bob S On Dec 8, 2014, at 09:29 , Ray r...@linkit.com wrote: I just issue the command quit. You might consider saving first or, if you don't want any interruptions, locking

Re: How to Quit with a button

.) Then a regular quit doesn't ask. On December 9, 2014 11:25:36 AM CST, Bob Sneidar bobsnei...@iotecdigital.com wrote: My perennial question is, how do I quit without saving the stack or even asking? There ought to be a “close without saving” variation. Bob S On Dec 7, 2014, at 15:25 , Colin

Re: How to Quit with a button

William Prothero wrote: On Dec 8, 2014, at 2:10 PM, Richard Gaskin wrote: Interesting. Any pending messages at the time quit is invoked? I tried doing “Lock messages” before the quit, and closing unused stacks, but it didn’t seem to make any difference. Apparently the toolbar menu quit

Re: How to Quit with a button

Richard: There really is no code in the quit button. I just do: ——Method 1 -- on mouseUp quit end mouseUp Or: ——Method 2 -- on mouseUp send “doTheQuit” to me in 0 seconds end mouseUp on doTheQuit quit end doTheQuit I tried closing all substacks. Do I need to close

Re: How to Quit with a button

William Prothero wrote: There really is no code in the quit button. I just do: ——Method 1 -- on mouseUp quit end mouseUp Or: ——Method 2 -- on mouseUp send “doTheQuit” to me in 0 seconds end mouseUp on doTheQuit quit end doTheQuit I tried closing all substacks. Do I need

Re: How to Quit with a button

My perennial question is, how do I quit without saving the stack or even asking? There ought to be a “close without saving” variation. Bob S On Dec 7, 2014, at 15:25 , Colin Holgate co...@verizon.netmailto:co...@verizon.net wrote: Try this instead: on mouseup quit end mouseup

Re: How to Quit with a button

Any open drivers also prevent quitting, or it used to. On December 9, 2014 8:59:32 AM CST, Richard Gaskin ambassa...@fourthworld.com wrote: William Prothero wrote: On Dec 8, 2014, at 2:10 PM, Richard Gaskin wrote: For an app to successfully quit two conditions must be met: 1. All stacks

Re: How to Quit with a button

Richard: Got your logger stack. I’m in a huge crunch right now, so I need to just go ahead and delete my quit button, and use the toolbar menu to quit, for a bit. I’m getting ready for a geophysics meeting in San Francisco, then Hawaii until Jan. 1. I’ll try to get to it but got a bunch

Re: How to Quit with a button

That only happens in the IDE, you can lock messages before quitting. Or, what I usually do from the message box: delete this stack. (Or you can use the menu option to remove from memory.) Then a regular quit doesn't ask. On December 9, 2014 11:25:36 AM CST, Bob Sneidar bobsnei

Re: How to Quit with a button

the message box: delete this stack. (Or you can use the menu option to remove from memory.) Then a regular quit doesn't ask. On December 9, 2014 11:25:36 AM CST, Bob Sneidar bobsnei...@iotecdigital.com wrote: My perennial question is, how do I quit without saving the stack or even asking

Re: How to Quit with a button

Jim, Great idea! There are s many ways to do things in LC. Bill On Dec 8, 2014, at 1:58 PM, Jim Lambert j...@netrin.com wrote: I suggested doMenu because Bill said selecting Quit from the menu worked while a button with ‘quit’ didn’t. But he reports that doesn’t work for him either, so

Re: How to Quit with a button

Prothero wrote: why won?t the button work when the toolbar menu does. Obviously, there?s a difference in the way each works. What happens if you doMenu “Quit” from menu [appName] ? Jim Lambert ___ use-livecode mailing list use-livecode

Re: How to Quit with a button

I just issue the command quit. You might consider saving first or, if you don't want any interruptions, locking messages first. On 12/8/2014 2:04 PM, Jim Lambert wrote: Prothero wrote: why won?t the button work when the toolbar menu does. Obviously, there?s a difference in the way each

  1   2   >