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://www.hyperactivesw.com
On June 7, 2018 11:28:18 AM Sannyasin Brahmanathaswami via use-livecode
<use-livecode@lists.runrev.com> wrote:
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
as "crashed" ; but on is dead-on-arrival - just the card 1 of the launcher
stack app, with logo.
Good think you caught this. I will have to let users on android force stop,
as the only choice.
BR
J. Landman Gay
I want to wipe the app completely so that on next launch I can
reinitialize everything.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
