Databases
StackOverflow2013
Postsdbo
POFragmentTransaction not doing anything
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFragmentTransaction not doing anything
    primarykey
    data
    text
    <p>I am learning fragments and below given is my first fragment program. A simple project where I have 2 screens. When I click the next button of first screen, second button needs to be shown. </p> <p><img src="https://i.stack.imgur.com/F8HyP.png" alt="enter image description here"></p> <p>I am targeting Android 2.1 and above and <strong>using compatibility package</strong></p> <h2>AppMainFragmentActivity.java</h2> <pre><code>public class AppMainFragmentActivity extends FragmentActivity { @Override protected void onCreate(Bundle arg0) { super.onCreate(arg0); setContentView(R.layout.app_main_layout); } } </code></pre> <h2>app_main_layout.xml</h2> <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:orientation="vertical" android:id="@+id/fragment_container"&gt; &lt;fragment class="com.research.fragmentstudy.FirstFragment" android:layout_width="fill_parent" android:layout_height="fill_parent" android:id="@+id/id_first_fragment"/&gt; &lt;/LinearLayout&gt; </code></pre> <h2>FirstFragment.java</h2> <pre><code>public class FirstFragment extends Fragment { @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View view = inflater.inflate(R.layout.first_fragment_layout , container,false); Button nextButton =(Button) view.findViewById(R.id.button); nextButton.setOnClickListener(nextListener); return view; } private OnClickListener nextListener = new OnClickListener() { @Override public void onClick(View v) { FragmentManager fm = ((AppMainFragmentActivity)FirstFragment.this .getActivity()).getSupportFragmentManager(); SecondFragment fragment = new SecondFragment(); FragmentTransaction ft = fm.beginTransaction(); ft.add(R.id.fragment_container, fragment); ft.commit(); } }; } </code></pre> <h2>first_fragment_layout.xml</h2> <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:orientation="vertical" android:id="@+id/first_fragment_root"&gt; &lt;TextView android:layout_height="wrap_content" android:layout_width="fill_parent" android:text="Fragment 1" android:gravity="center_horizontal" /&gt; &lt;Button android:layout_height="wrap_content" android:layout_gravity="center_horizontal" android:layout_width="wrap_content" android:id="@+id/button" android:text="Next" /&gt; &lt;/LinearLayout&gt; </code></pre> <h2>SecondFragment.java</h2> <pre><code>public class SecondFragment extends Fragment { @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View view = inflater.inflate(R.layout.second_fragment_layout, container,false); return view; } } </code></pre> <h2>second_fragment_layout.xml</h2> <pre><code>&lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent" android:orientation="vertical" android:id="@+id/first_fragment_root"&gt; &lt;TextView android:layout_height="wrap_content" android:layout_width="fill_parent" android:text="Fragment 2" android:gravity="center_horizontal" /&gt; &lt;/LinearLayout&gt; </code></pre> <p>Well I am getting the first screen alright. Now,</p> <h3>What I expected, from my understanding of fragment</h3> <ul> <li>When I click the Next button in screen 1, SecondFragment is created, its <code>onCreate()</code> and <code>onCreateView()</code> gets called.</li> <li>SecondFragment is shown, and FirstFragment gets destroyed (since I am not adding it to backstack). There won't be any animation since default fragment transaction doesn't have animation.</li> </ul> <h3>What is happening</h3> <ul> <li>SecondFragment is getting created alright, its <code>onCreate()</code> and <code>onCreateView()</code> gets called.</li> <li>But FirstFragment remains on the screen, and second one never showing.</li> </ul> <p>Now my understanding of fragment can be wrong. But I believe when we commit() a fragment transaction, first fragment should be replaced by second one (first one either gets hidden or destroyed). Well nothing seems to be happening. Why is that? Should we manually destroy/hide first fragment?</p> <p>Note : I know it is a long question for such a basic thing. But I put my entire code since I am not sure where I messed it up. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKrishnabhadra
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFragmentTransaction not doing anything
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POFragmentTransaction not doing anything
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POFragmentTransaction not doing anything
      1. USShajeel Afzal
      1. VTFavorite
    1. This table or related slice is empty.
 

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