On Jan 16, 8:06 pm, Subba wrote:
> My application has two activities A, B.
>
> Initially application launches with A activity(root activity), and
> then it launches the B activity and finishes A activity. Now B
> activity on the foreground.
> User pressed Home Button on B activity it launches HOM
Doug,
I followed the document all the cases it works. However when
ever i launch home screen from my app, activity stack remembers old
activities(B,A), if i launch again the application using launcher, i
am not able fix that. Please suggest.
On Jan 16, 10:41 pm, Doug wrote:
> On Jan
Are you looking for a practical answer? Or was this more of a
"theoretical" thought experiment type of question?
If you want the practical answer, then I guess the simple thing to do
would be to kill Activity A in it's onActivityResult method (which
should be overridden since you are calling start
I am also facing the same problem in my application in my application
A starts B and B starts C now C is on the screen and i want to close
the complete app in just a single click of button.
Manoj Chauhan
--
You received this message because you are subscribed to the Google
Groups "Android Deve
Hard to do without changing code. I always end having to implement
logout(), so all my activities extend a custom base activity, and in
that base activity in onCreate I always end up checking for a global
static:
if(!isLoggedIn){
finish();
return;
}
On Jan 6, 4:43 am, Zhihong GUO wrote:
>
check setFlags in Intent class. Also read
http://developer.android.com/guide/topics/fundamentals.html#acttask
You can clear the stack upto a particular activity, if you want you
can also set that your activity A is never kept in stack.
HTH
On Mar 4, 2:23 am, Sam wrote:
> So I have an app with A
Thanks for the info, but no of those intent combination I can seem to
get to work.
Basically if I have,
A(1)->A(2)->A(3)->A(4)
And when A(4) starts, I want A1-3 to be cleared from the stack.
On Mar 3, 4:37 pm, A R wrote:
> check setFlags in Intent class. Also
> readhttp://developer.android.co
Did you try singleTop, singleTask or singleInstance?
In your situation, you may need to maintain an intent stack all by
yourself from A1 through A3, and handle the BACK key event
respectively
http://d.android.com/guide/topics/manifest/activity-element.html#lmode
On Mar 3, 11:58 pm, Sam wrote:
>
I ended up following someones suggestion of using an Activity stack to
handle things similiar to your intent stack to manage the 'Back' key
event thanks.
On Mar 3, 6:10 pm, Bo wrote:
> Did you try singleTop, singleTask or singleInstance?
>
> In your situation, you may need to maintain an intent s
9 matches
Mail list logo
