Databases
StackOverflow2013
Postsdbo
POTabs inside another Tab( using Fragments) in Android
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTabs inside another Tab( using Fragments) in Android
    primarykey
    data
    text
    <p>In my app(android 2.1), i have successfully added tabs using Fragments and I use Android Compatibility library v4.</p> <p>Now i want to add another tab inside one of the fragment tabs, but the tabwidget throws NullPointerException, what i am doing wrong here?</p> <p>LogCat:</p> <pre><code>05-08 12:58:57.060: W/dalvikvm(1371): threadid=3: thread exiting with uncaught exception (group=0x4001b188) 05-08 12:58:57.060: E/AndroidRuntime(1371): Uncaught handler: thread main exiting due to uncaught exception 05-08 12:58:57.100: E/AndroidRuntime(1371): java.lang.NullPointerException 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.widget.TabWidget.dispatchDraw(TabWidget.java:206) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.View.draw(View.java:6538) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1531) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.View.draw(View.java:6538) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.support.v4.view.ViewPager.draw(ViewPager.java:1574) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1531) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1529) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.View.draw(View.java:6538) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.widget.FrameLayout.draw(FrameLayout.java:352) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.drawChild(ViewGroup.java:1531) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.View.draw(View.java:6538) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.widget.FrameLayout.draw(FrameLayout.java:352) 05-08 12:58:57.100: E/AndroidRuntime(1371): at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1830) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewRoot.draw(ViewRoot.java:1349) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewRoot.performTraversals(ViewRoot.java:1114) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.os.Handler.dispatchMessage(Handler.java:99) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.os.Looper.loop(Looper.java:123) 05-08 12:58:57.100: E/AndroidRuntime(1371): at android.app.ActivityThread.main(ActivityThread.java:4363) 05-08 12:58:57.100: E/AndroidRuntime(1371): at java.lang.reflect.Method.invokeNative(Native Method) 05-08 12:58:57.100: E/AndroidRuntime(1371): at java.lang.reflect.Method.invoke(Method.java:521) 05-08 12:58:57.100: E/AndroidRuntime(1371): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860) 05-08 12:58:57.100: E/AndroidRuntime(1371): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618) 05-08 12:58:57.100: E/AndroidRuntime(1371): at dalvik.system.NativeStart.main(Native Method) </code></pre> <p>// sub tab fragment</p> <pre><code>import android.os.Bundle; import android.support.v4.app.Fragment; import android.view.LayoutInflater; import android.view.View; import android.view.ViewGroup; import android.widget.LinearLayout; public class Tab3Fragment extends Fragment { public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { if (container == null) { // We have different layouts, and in one of them this // fragment's containing frame doesn't exist. The fragment // may still be created from its saved state, but there is // no reason to try to create its view hierarchy because it // won't be displayed. Note this is not needed -- we could // just run the code below, where we would create and return // the view hierarchy; it would just never be used. return null; } return (LinearLayout)inflater.inflate(R.layout.subtab, container, false); } </code></pre> <p>}</p> <p>// subtab.xml</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent" android:background="#4C4C4C" &gt; &lt;TabHost android:id="@android:id/tabhost" android:layout_width="fill_parent" android:layout_height="fill_parent" android:padding="2dp"&gt; &lt;LinearLayout android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent" android:padding="5dp"&gt; &lt;TabWidget android:id="@android:id/tabs" android:layout_width="fill_parent" android:layout_height="wrap_content" /&gt; &lt;FrameLayout android:id="@android:id/tabcontent" android:layout_width="fill_parent" android:layout_height="fill_parent" &gt; &lt;/FrameLayout&gt; &lt;/LinearLayout&gt; &lt;/TabHost&gt; &lt;/LinearLayout&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRaneez Ahmed
    1. USRaneez Ahmed
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POTabs inside another Tab( using Fragments) in Android
      1. USsimha
      1. VTFavorite
    1. COA tab within a tab? This sounds somewhat complex to me... are you certain there isn't an easier way to organize your app? (I'm not saying you are incorrect, I'm just saying it might be worth considering).
      singulars
      1. POTabs inside another Tab( using Fragments) in Android
      1. USAlex Lockwood
    2. COAlso, you define your xml schema twice (`xmnls:android`). You only need to do this once in the parent layout.
      singulars
      1. POTabs inside another Tab( using Fragments) in Android
      1. USAlex Lockwood
    3. COxml schema was a mistake but that is not the problem here. I have done this using TabActivity. I'm now implementing with Fragments as TabActivity is deprecated.
      singulars
      1. POTabs inside another Tab( using Fragments) in Android
      1. USRaneez Ahmed
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload