Hello,
I am still waiting and hoping for some suggestions on single instance.
As per my experiments results, either I have not understood Google
documentation properly or its behavior is different from Google
documentation.
Kindly suggest.
Thanks,
Vibhor
On Tue, Jun 22, 2010 at 3:00 PM,
On Thu, Jun 24, 2010 at 9:40 AM, Vibhor Mahajan
mahajan.vib...@gmail.com wrote:
I am still waiting and hoping for some suggestions on single instance.
As per my experiments results, either I have not understood Google
documentation properly or its behavior is different from Google
So far as I have explained what you say you are seeing is consistent with
the intended behavior, and how I believe it is documented.
You need to read through all of the documentation on launch modes, tasks,
taskAffinities, and activity stacks. The singleInstance mode imposes
constraints on the
Hello,
Thanks Dianne for reply. I understood your point. But after doing some more
tests I have confusions. Kindly provide some suggestions.
Activity A has SINGLEINSTANCE and B C has STANDARD launch mode.
Execute below steps:
1. Start A from launcher
2. Launch B from A. (oncreate of B is
Yes that is working as intended, you have B and C together in their own
task, and A can't be in it because it is single instance.
Again, just ignore single instance unless you have a clear reason for using
it, and then you will want to structure the rest of your interaction to work
well with it.
Hello,
Simply saying, I am trying to understand the behavior of singleinstance in
detail. I found 2 different behaviors when a activity with singleinstance
launchmode, launches an another activity.
Based on your reply, I understood SINGLEINSTANCE activity is launching an
activity in new task and
Actually,
to me it sounds it's behaving correctly...
If Activity B is standard then it might be re-used, so it's not
obliged to create a new Instance...
Thats what happens in ur case, first time it get's created, then you
go to activity A, then when you ask for Activity B the old activity
B is
Btw, got this from documentation, concentrate on the last sentence :
Every time there's new intent for a standard activity, a new
instance of the class is created to respond to that intent. Each
instance handles a single intent. Similarly, a new instance of a
singleTop activity may also be created
Hello,
As per the documentation, standard and singletop differ in just one way,
standard activity instance is created every time but singletop instance may
or may not be created. I verified this, if in the above code, reverse
launchmode of activity A B i.e. Now A has STANDARD and B as
First, you almost certainly don't want to use singleInstance. It is for
very special situations, and has significant repercussions on UI flow that
you need to understand before touching it.
The key point about this is this statement in Launch modes
10 matches
Mail list logo
