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 the complexit
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
Jacque said: "I want to wipe the ap
o use LiveCode
Cc: Sannyasin Brahmanathaswami
Subject: 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 spl
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://ww
2:26 PM
To: How to use LiveCode
Cc: Sannyasin Brahmanathaswami
Subject: 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
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" ; does not appear to user a
