Databases
StackOverflow2013
Postsdbo
POIs this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
    primarykey
    data
    text
    <p>I'm using the Android Compatibility library to implement fragments and have extended the layout sample so that a fragment contains a button which fires off another fragment.</p> <p>In the selection pane on the left I have 5 selectable items - <code>A B C D E</code>.</p> <p>Each loads up a fragment (via <code>FragmentTransaction:replace</code>) in the details pane - <code>a b c d e</code></p> <p>Now I've extended fragment <code>e</code> to contain a button which loads up another fragment <code>e1</code> also in the details pane. I've done this on fragment <code>e</code>'s onClick method as follows:</p> <pre><code>FragmentTransaction ft = getActivity().getSupportFragmentManager().beginTransaction(); ft.replace(R.id.details_frag, newFrag); ft.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_OPEN); ft.addToBackStack(null); ft.commit(); </code></pre> <p>If I make the following selections:</p> <pre><code>E - e - e1 - D - E </code></pre> <p>Then fragment <code>e</code> is in the details pane. This is fine and what I want. However, if I hit the <code>back</code> button at this point it does nothing. I have to click it twice because <code>e1</code> is still on the stack. Furthermore after clicking around I got a null pointer exception in onCreateView:</p> <p>To 'solve' this problem I added the following whenever <code>A B C D E</code> is selected:</p> <pre><code>FragmentManager fm = getActivity().getSupportFragmentManager(); for(int i = 0; i &lt; fm.getBackStackEntryCount(); ++i) { fm.popBackStack(); } </code></pre> <p>Just wondering whether this is the correct solution or whether I should be doing something different?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMogsdad
    1. USPJL
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    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. POIs this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
      1. This table or related slice is empty.
      1. VTUpMod
    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