Gerry, thanks for replying. That's what happens to my simple little app, but what about my favourite radio app, TuneIn Radio? It's feeding the BBC to me as I write this, but I could only access Mail by pressing the Home button after getting my radio station started, and it was definitely not killed. I'm sure there are lots of other examples... what is going on in these cases?
Graham Sent from my iPad On Sun, 19 Feb 2012 21:44:09 +1100, Gerry Orkin <gerry.or...@gmail.com> > LC iOS apps don't stay alive when you quit them with the Home button. You can > save and restore things to give the impressions of a quit and resume, but the > app itself is killed when you quit. > > In my experience the "on shutdown" command is the best place to put stuff you > want to do when the app quits. > > > Gerry > > > > > > On 19/02/2012, at 8:39 PM, Graham Samuel wrote: > >> AFAICS, iOS apps don't have an overt 'quit' button, since simply pressing >> the physical button on the device (I forgot its name) quits whatever is >> running. However this isn't quite right is it, since apps can go on being >> present and maybe actually running in the background. And then there is the >> question of what happens when your app gets itself into an unexpected state >> and has no alternative but to exit, which presumably would mean using a >> 'quit' command. Again, from the slender evidence I have, an explicit 'quit' >> may cause iOS to restart your app, tho not apparently in all circumstances. >> I have not yet found out the difference between stopping and leaving the app >> running in the background and really killing the app. >> >> Has anyone a clearer picture of how and why one would use 'quit' in the >> script of an iOS app? >> >> 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
