Android has always acted like this and now that iOS apps run in the
background like Android does, it behaves the same way. At least our
problems are cross-platform now.
An app will stay in RAM until the user specifically quits or until the OS
needs the memory. When that happens, the OS wipes the app and it
effectively shuts down. We get no warning, except for a shutDown message.
Android recommends we store the last state of the app and restore it when
it starts up again.
I'd love to get a message when the app goes into the background but so far
there is none. Storing every little change as it happens seems tedious and
wasteful. I haven't had much luck with storing changes on shutdown but it's
worth a try, it's been a while since I did it.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 17, 2020 9:27:50 AM Graham Samuel via use-livecode
<use-livecode@lists.runrev.com> wrote:
Sorry if this is documented somewhere but I can’t find it.
On desktop platforms, LC gives us “suspend” which is fired when the app
goes into the background. I seem to be having some problems with iOS, in
that when the screen locks (triggered by user action or a time limit), my
app seems to stop getting messages from the OS, so is in some sense
suspended. This seems to call for something like “suspend” for mobiles.
Does such a message exist?
Another thing that happens with iOS apps that use Location Services is that
the user is sometimes asked via a popu-up on the screen of the device
whether the app should be allowed to use these services when it’s not
running. I don’t know what triggers these user messages, nor am exactly
certain what ‘not running’ means - presumably if the app has been properly
quit, that’s something other than ‘not running’. In the Standalone Settings
for mobile, one can set Location Services as being a requirement, but there
doesn’t seem to be a setting corresponding to this user choice.
Has anyone a clear understanding of all this? I would love to see an
explanation.
TIA
Graham
_______________________________________________
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
