Re: [android-developers] Further Info

2010-08-25 Thread Kostya Vasilyev
Since the Activity is your own, add a call to finish() in onCreate, after starting the service and the next activity. -- Kostya Vasilyev -- http://kmansoft.wordpress.com 25.08.2010 4:32 пользователь Call_Waiting team.mu.capt...@gmail.com написал: This is what I found from in my researching

[android-developers] Further Info

2010-08-24 Thread Call_Waiting
This is what I found from in my researching (ActivityManager.RunningAppProcessInfo) too. Hackborn I think your on the right train of thought. I just want to peek() at the top of the Activity Stack. So I know when the user has left the app that my app started. Currently you have to go back to

Re: [android-developers] Further Info

2010-08-24 Thread Dianne Hackborn
As I've said, relying on these functions for control flow will not be robust. And that isn't even mentioning what happens tomorrow when... say... we add support for multiple running activities at a time. Which one is the top then? On Tue, Aug 24, 2010 at 5:32 PM, Call_Waiting

Re: [android-developers] Further Info

2010-08-24 Thread Frank Weiss
Your terminology is quite bit confusing. You seem to use the term app to mean activity. I assume the scenario you are trying to describe is based on: your app has an activity A and a service B, and another app has an activity C. When activiity A is CREATED [emphasis mine] it starts service B