jarkman wrote: > Well, it didn't seem insane on 1.1, and it ran happily enough. Let me > break it down for you, and see if it makes any more sense. > > From the top, in HierarchyViewer, reading down the deepest path, we > go: > > PhoneWindow$DecorView > LinearLayout > FrameLayout > TabHost > LinearLayout (comes with the TabHost) > FrameLayout (comes with the TabHost) > PhoneWindow$DecorView > FrameLayout (for this tab) > LinearLayout > FrameLayout (also holds a loading-progress gizmo) > FastScrollView > ListView > RelativeLayout (for the list item) > OurPhotoView > ImageView
My guess from this list is that are using the embed-an-activity-in-a-tab stuff, which is why you get the second PhoneWindow$DecorView and, possibly, the subsequent FrameLayout. If my guess is correct, you could alter your application to not use activities in this fashion and save 1-2 levels in your view hierarchy. Populate your tabs via Views (possibly using the factory pattern for a faster initial open) instead of activities. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, $35/Year --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
