How to quit an Android app

[J. Landman Gay]

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 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 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
>>
>>
>>
>>
>> On 12/20/16, 9:38 PM, "use-livecode on behalf of J. Landman Gay"
>> <use-livecode-bounces at lists.runrev.com on behalf of
>> jacque at hyperactivesw.com> wrote:
>>
>>> 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?


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com