[iOS] Suspending and quitting

Dar Scott dsc at swcp.com
Sat Mar 3 19:34:26 EST 2012


I'm still learning how things are supposed to be on iOS, so this is just a thought.  I think you almost always "suspend" unless the user pushed a button on the app to "quit".  I can't point to any guidelines.  Maybe there is some clear function that can also bring the state of the app to the same as after a "quit".

Dar

On Mar 3, 2012, at 1:50 PM, J. Landman Gay wrote:

> I have code in my iOS app that fakes a "suspend" so it can pick up where the user left off when they come back to the app. Now I'm trying to figure out when to use it.
> 
> Is it logical to assume that if the user presses the Home button, they mean to quit? And if they push up the window to switch to another app, they mean to suspend? And if that's true, how would I know when the Home button is pressed? I don't think it's possible.
> 
> Also, if the app is "resuming" I don't want the splash screen to show, the app should just appear in the state the user left it. Is there a way to avoid the splash?
> 
> How do you handle the situation in general?
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode






More information about the use-livecode mailing list