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: > >tsNetClose >wait 1

RE: How to quit an Android app

ay, December 22, 2016 5:43 PM To: How to use LiveCode Subject: 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

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 >quit > > Success! :) I would

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

Hi, ignore my last posting. Just noticed that you wrote about that possiblitiy already. > Am 21.12.2016 um 18:05 schrieb Matthias Rebbe > >: > > Hi, > > just a shot in the dark, but did you try tsNetClose before

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 : > > Sending "quit" in 10 milliseconds doesn't crash the app on second launch

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" isn't long enough? I'm

Re: How to quit an Android app

Yeah, I tried that. Maybe "in 0" isn't long enough? I'm wondering if it's TSNet, since the app loads another stack from a server. On the second launch that crashes, I see the loader stack briefly and it crashes when it tries to download the remote stack. There's a way to remove TSNet from

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"

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 standalone?