I guess it depends on the app. A role player shootemup game for instance, would
be poorly designed if a player could simply bail at the last possible moment
and relaunch to avoid a bad score. Al accounting app however might want to have
the user log in from the start for security reasons.
Bob
t apps deal with it differently. As long as their method is
reasonably logical, I don't really mind as long as I don't lose data.
My 2 cents
Kelly
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/iOS-Suspending-and-quitting-tp4442267p4443021.html
Sent from
On Sun, Mar 4, 2012 at 1:17 PM, J. Landman Gay wrote:
> Maybe others don't see it that way. That's part of what I'd like to know.
>
> If I was on your Settings card, and pressed the Home button so I could
send and SMS (which is how I always get to Messages) when I return to your
game I'd expect to
When I touch an app icon, the splash image expands and then the app shows the
first card.
I usually leave an app by the five finger pull. The image of the current card
shrinks. This is similar to the shrink of pushing the home button.
If I use the four-finger flip to the side to switch apps
On 3/3/12 6:42 PM, Matthias Rebbe wrote:
Hi Jacque,
couldn´t you add an user option in the settings of the app e.g. "always resume from
where i left…".
If the user checks this option, the app always resume to the last opened card.
If not checked, the app starts with the first card.
So the use
On 3/3/12 10:22 PM, Dar Scott wrote:
I apologize. I was not clear.
I was trying to suggest that one can design the app so that every
launch is a virtual resume.
That could work but in this case it isn't ideal. I'm thinking of my
solitaire game. The main card is the gameboard. The other cards
On Sun, Mar 4, 2012 at 11:08 AM, Gerry Orkin wrote:
>
> I've never seen an iOS app with a quit button.
>
> Same here. Nor have I seen any app that behaves differently depending on
how you leave, only if you really Quit or not.
Some apps (eReaders particularly) always return you to where you left
I apologize. I was not clear.
I was trying to suggest that one can design the app so that every launch is a
virtual resume.
Dar
On Mar 3, 2012, at 8:08 PM, Gerry Orkin wrote:
> Dar Scott wrote:
>
>> I think you almost always "suspend" unless the user pushed a button on the
>> app to "qu
Dar Scott wrote:
> I think you almost always "suspend" unless the user pushed a button on the
> app to "quit". I can't point to any guidelines.
LC iOS apps don't suspend - they only quit. We might get the ability to suspend
them in the future, but we don't have it right now.
I've never seen
Hi Jacque,
couldn´t you add an user option in the settings of the app e.g. "always resume
from where i left…".
If the user checks this option, the app always resume to the last opened card.
If not checked, the app starts with the first card.
So the user might not be confused.
Regards,
Matthi
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 sam
Oh right, sorry...misunderstood. No, you can't tell the method by which the
user has switched or quit from an app, as far as I've been able to tell. But
it's probably not a big issue - I don't think the average user uses the "task
list" method of switching to other apps.
Gerry
On 04/03/2012,
On 3/3/12 5:46 PM, Terry Judd wrote:
I don't think you can. My apps use logins and session tokens so if
the user 'restarts' the app while the session token is still valid I
ask them whether they want to resume or start afresh.
Thanks, I guess I'll keep it as it is. It just looks funny when the
On 04/03/2012, at 10:17 AM, J. Landman Gay wrote:
On 3/3/12 4:40 PM, Gerry Orkin wrote:
I'm pretty sure you can't suppress the splash screen.
Yes, sounds that way.
As for the best place to run your code for saving the current state
of the app...I use the shutdown message.
I'm doing that too,
On 3/3/12 4:40 PM, Gerry Orkin wrote:
I'm pretty sure you can't suppress the splash screen.
Yes, sounds that way.
As for the best place to run your code for saving the current state
of the app...I use the shutdown message.
I'm doing that too, but I need a way to know when to reload the sav
I'm pretty sure you can't suppress the splash screen.
As for the best place to run your code for saving the current state of the
app...I use the shutdown message.
Gerry
-- Sent from my iPhone.
___
use-livecode mailing list
use-livecode@lists.runre
On 3/3/12 2:58 PM, Scott Rossi wrote:
Recently, Jacque Landman Gay wrote:
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?
Isn't this a case where you avoid the splash screen se
Recently, Jacque Landman Gay wrote:
> 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?
Isn't this a case where you avoid the splash screen setting of the SB and
show your own sp
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
19 matches
Mail list logo
