Wednesday, April 27, 2011

[android-developers] Orphaning a Task

The doc says this:

http://developer.android.com/guide/topics/fundamentals/tasks-and-back-stack.html

"This second ability is important: Users must be able to leave a task
and then come back to it later using this activity launcher. For this
reason, the two launch modes that mark activities as always initiating
a task, "singleTask" and ""singleInstance", should be used only when
the activity has an ACTION_MAIN and a CATEGORY_LAUNCHER filter.
Imagine, for example, what could happen if the filter is missing: An
intent launches a "singleTask" activity, initiating a new task, and
the user spends some time working in that task. The user then presses
the HOME key. The task is now sent to the background and not visible.
Because it is not represented in the application launcher, the user
has no way to return to the task."

But isn't it true that the user could indeed navigate back to that
'singleTask' task by simply following the steps they took to get there
in the first place, when they first launched it? There will obviously
not be a launcher icon for this task, but if the user launched
whatever they launched in the first place, and then performed the same
action that started the task in the first occurrence, then the system
should find the existing task and bring it to the foreground correct?
Or does Android destroy tasks that it considers 'orphaned'?

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate