I'm sorry to say that this is still a problem. We are trying to create an application with a very location-centric workflow. The problem is that we need tabs which you can navigate inside of, but the workflow is rather complex and we do not want to use an ActivityGroup for that reason (unmaintainable at this scale).
So we've decided to use the Fragments API, which I take it was kind of designed for this reason (I remember the documentation saying something to that effect). This allows me to have one activity representing the tabs workflow, but to have the fragments like mini activities inside the tab's hosted activity (complete with back stack). The problem is that with multiple fragments in the same activity, if you have already shown a MapView on a fragment, that fragment may still live somewhere in the backstack. Showing another fragment with a MapView kills your app because the other one still exists (even if hidden). Or am I doing something else wrong? Karl On Apr 29, 5:15 pm, Karl Wagner <razie...@gmail.com> wrote: > Any news on a way to get a MapView on to a fragment? I would have > thought this was really quite an urgent flaw (it you're using > fragments, it really messes up your app's workflow) > > I'm using the compatibility library, and the current way of doing > things by extending making FragmentActivity extend MapActivity is > horrible because you will eventually get a "two mapviews on one > mapactivity" error. -- 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
