On 3/2/2013 1:32 PM, John Coryat wrote:
>> it sounds like the bug on your side (no offense and sorry if I misunderstood the
problem)...
The problem isn't our app, it's the state of Android introductory
orientation. If users don't know how to properly end apps, then they
can run into all kinds of problems. Case in point are task killers.
Perhaps the reason these are so popular is that their users just don't
know what the back key is for.
Sorry but I have to agree that back and home should behave mostly
identically from a user perspective. Nor should I need to "back" out of
20 activities/states on the stack to kill takes. Android manages memory
by killing processes when it doesn't have enough free RAM, and that
includes processes on the task stack. And it DOESN'T kill a process (at
least it didn't when I checked last) just because you hit "back," though
your app may be getting an onCreate() instead of an onNewIntent() when
the new "task" is started (most of my apps live at the NDK layer, so I'm
PAINFULLY aware of when the APP gets killed, as opposed to the Activity
getting started or stopped -- I would see things like onDestroy() being
called AFTER onCreate() for the "new" task, but all in the same process).
Doing a refresh in onResume() should fix the "bug", as mentioned above,
which is probably a good way to fix the user perception of updates,
regardless of whether the user is being an idiot and not clicking the
obvious "refresh" button -- and that's a good thing regardless of
whether you believe me as to how an app "should" work. ;)
Tim
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/android-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
