Mark, so I'm confused. No, the activity was not destroyed, but it went in the background when the CameraActivity was started with an intent -- do I need to shove the state in manually an instance variable of an Application subclass? I guess that would be a solution. I guess another solution is to send the state from Activity A to Activity B and back again when Activity A comes to the foreground.
This seems sort of bass ackwards. On Aug 31, 4:26 pm, Mark Murphy <[email protected]> wrote: > bkbonnerwrote: > > To reiterate, onPause and onSaveInstanceState gets fired, but > > onRestoreInstanceState is never fired when coming back from the > > CameraActivity. > > If your activity was not destroyed, you should already have your state, > and onRestoreInstanceState() will not be called. This is similar to the > following: > > http://stackoverflow.com/questions/1354524/android-problem-with-savin... > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Beginning Android_ from Apress Now Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
