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 complexities of the Android OS, and Ralph was right
that the problem was a null pointer.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 9, 2018 8:32:18 AM Sannyasin Brahmanathaswami via use-livecode
<use-livecode@lists.runrev.com> wrote:
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 app completely so that on next launch I can
reinitialize everything"
Hmmm. Tell turn your users to "Force Quit" in order re-init.
Ugly UI, of course. But there are certain processes where the OS wants to
re-boot.
What fight it?
BR
?On 6/7/18, 8:01 AM, "use-livecode on behalf of J. Landman Gay via
use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of
use-livecode@lists.runrev.com> wrote:
It could be solved if we had suspend and resume messages but I heard this
is difficult to implement on Android.
_______________________________________________
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
