Nevermind...sorta...the solution was to move the UI rebuilding routine from onActivityResult to onResume. The problem seemed to stem from the exactly order in which onCreate, onActivityResult, and onResume are called upon return to the primary activity. Cuidado! :-)
On Jan 5, 10:09 am, Keith Wiley <kbwi...@gmail.com> wrote: > Here's an interesting dilemma. My app detects and reacts to > orientation changes (through a screen-flip-open/close on the G1 for > example) through the onPause/onResume/onCreate methods without any > trouble. It handles them and keeps rolling with the correct > behavior...but, if someone opens a second, temporary activity, for > example, the preferences activity incorporated into my app, and then > flips the orientation while in that secondary activity, and then > closes it to return to the primary activity, then my program crashes, > and I have determined that the problem is that the primary activity > didn't receive a onPause/onResume/onCreate call and consequently > didn't rebuild its UI properly. > > What's the proper way to handle this? Do I have to manually send a > message from the secondary activity when it notices the orientation > flip to the primary activity so it knows to rebuild itself? > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
