To say that TabHost not working without deriving from TabActivity is not a bug is a bit strange. Buttons do not require the activity to derive from ButtonActivity to not crash, do they? And it's not lilke a car not working without fuel. It's more like a car not working because there are other cars on the road. A tab control is not some new UI design unique to Android that only makes sense in a very specific context, so it's not unreasonable to expect it to work like every other UI elements : I should be able to place one in my layout wherever I want, or maybe even have two of them in the same layout, and it should not crash. I should be able to get the selected tab of each of them individually, and do whatever processing I wish based on that information.
That aside, what skinks mention is precisely where my problem lies : the call to setup() crashes. I've seen another post where someone posted their XML layout, and they had manually added a TabWidget and FrameLayout with specific android IDs as children of the TabHost. I thought from reading the docs that creating those was what setup was for. It seems like a really bad idea to manually build UI elements that are OS dependent, since some future version might have different internal requirements and the app would no longer work. So the question remains. Which of the following applies : 1. It is a bug (ie. Some future OS version will fix it). 2. TabHost will never work outside of TabActivity. (It should then be removed from the classes creatable in the layout editor) 3. It works, but there is something I'm supposed to call on it/add in the XML that I missed or isn't in the docs. (For example, it cannot be a child of a LinearLayout) 4. Nobody knows. It works perfectly fine for other people, and I'm just unlucky. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
