thanks bob for your reply. i do understand it doesn't doesn't mean i don't have to handle activity lifecycle, but not having to deal with the entire activity being destroyed and recreated seems useful.
I am definitely getting the correct version of the layout -- i tried changing something in the landscape version and it picked it up. On Apr 7, 8:18 am, Bob Kerns <[email protected]> wrote: > This doesn't save you from ANY of the complexities of the activity > lifecycles. > > It only removes SOME of the reasons you'll transition through them. > You should still code for the lifecycle. > > It makes your job harder, because not only to you get to debug your > current problem -- you lose an easy way to test your handling of the > activity lifecycle! > > One thing I'd check is if you're reliably getting the right > orientation's version of your layout. Try changing the background > color or some text, so you can reliably tell them apart, even if mis- > rendered. I don't see why that would be the problem, but it'd be good > to help make sure you're looking for the right problem. > > On Apr 7, 7:04 am, sdphil <[email protected]> wrote: > > > hi, i have a question regarding rotation. > > > I am looking into using: > > > android:configChanges="orientation|keyboardHidden" > > > in my manifest file for an activity in my application. that of course > > is accompanied with -- > > > @Override > > public void onConfigurationChanged(Configuration newConfig) { > > super.onConfigurationChanged(newConfig); > > setContentView(R.layout.myContentView); > > } > > > I am doing this for a layout that has a landscape version of that > > layout as well (i.e. I have a myContentView.xml in layout-land > > directory). The issue is that when I do this, sometimes it appears as > > though it doesn't render properly when going to landscape mode. I > > have two edit boxes on that page that sometimes don't appear. Usually > > it works, but sometimes they just disappear (or are off screen?). > > Anyway, I can't figure out why they don't get rendered. Any ideas on > > what i need to be doing here to make them render consistently? > > > My follow up question is why shouldn't I just do this for every > > activity (assuming it worked :-)? Then I could avoid much of the > > complexity surrounding activity lifecycle (I saw some issues regarding > > menus, but it seems like that could be overcome). > > > tia. > > -- 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 To unsubscribe, reply using "remove me" as the subject.
