I sugggest you have a look at this you example actually fairly represent this example android tabhost tutorial I hope you have seen it already.... this was the one I used when I frist developed my first android tab widget PS: Do have a look at this example part 2 of the above ... continuation each and everything you need to know.
I sugggest you have a look at this.... you example actually fairly represent this example.... android tabhost tutorial I hope you have seen it already.... this was the one I used when I frist developed my first android tab widget... PS: Do have a look at this example part 2 of the above ... continuation each and everything you need to know.
Thanks! I'm gonna have a look at this first thing in the morning... – nubicurio 2 days ago did it solve your problem... if yes would you mind indicating my answer as the answer to your problem.. if no... can you please tell me what you have tried, – medampudi 20 hours ago.
Looking at your code and your XML I think the problem is with the tab1. Xml with this line.
The buttons do show up on tab2 now; however, the text "@string/text" in tab1 is no longer visible:( – nubicurio 2 days ago Yeah that's a different problem with your layout, you should mark the answer in this thread and ask a new question for the new problem. – C0deAttack yesterday I probably did something else too, but I changed android:src to android:background that fixes my problem... – nubicurio 4 hours ago.
Remove the following two lines from the FrameLayout in your main. Xml and see what happens.
The reason is that you are adding views multiple times. The layouts from tab1. Xml and tab2.
Xml are being added automatically when you call setContentView(R.layout. Main) but then you are creating TabSpecs the first of which contains the TextView (tab1content) from tab1. Xml and the second contains the whole layout from tab2.
Xml (tab2content). When you call spec. SetContent(...) you are manually repeating inflations of the layout file contents that setContentView(R.layout.
Main) has already done because of elements in main.xml. – MisterSquonk 2 days ago I took out the include files and the app won't start at all (forced close); strangely I seem to have the fix the problem by changing android:src to android:background. But what you made makes a lot of sense...does that mean I actually have 4 tabs even though I'm only seeing two?
I don't know what I'm doing anymore:( – nubicurio 4 hours ago No - you have two tabs but I think you're adding in some of the tab content twice to each tab. You don't need anything in your FrameLayou unless you want it to appear in every tab. One thing I don't understand is using in the tab1.
Xml why isn't it just a standard LinearLayout? I also don't understand why removing the elements would cause force close - as I said you don't need anything in the FrameLayout in the XML file - trace the exception which is causing it. – MisterSquonk 3 hours ago.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.