It's not just what I need to remember, the other action is sending me data which I get in onActionComplete. Any thoughts?
On Aug 22, 3:05 pm, Dianne Hackborn <[email protected]> wrote: > That is the normal behavior -- your app is in the background, not relevant > to what the user is currently doing, so its process may be killed to use > memory elsewhere. You deal with this by implementing onSaveInstanceState() > to note anything to need to remember and collecting that from the state you > later receive in onCreate(). > > On Fri, Aug 21, 2009 at 6:47 PM, Timothy DeWees <[email protected]>wrote: > > > > > > > Hello, > > > I'm hoping for some help on ways to solve a problem. From my > > application, I launch an intent that returns a result I need to read > > (Zebra Crossing). But if the user takes a while to scan the barcode > > (low light, wobbly hands, etc), my main intent is getting killed. > > When the app re-launches, I'm not hitting the event for the intent > > returning. > > > Is there some start parameter to tell me the app is being re-launched > > and returning from a child intent? > > > Any suggestions on this would be helpful! > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
