Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>* EDIT *</strong></p> <p>As @ElliotM pointed out, there is a better solution. No need to change anything in your adapter, just get the fragment with:</p> <pre><code>Fragment myFragment = (Fragment) adapter.instantiateItem(viewPager, viewPager.getCurrentItem()); </code></pre> <p><strong>* OLD SOLUTION *</strong></p> <p>Best option is the second solution here: <a href="http://tamsler.blogspot.nl/2011/11/android-viewpager-and-fragments-part-ii.html" rel="noreferrer">http://tamsler.blogspot.nl/2011/11/android-viewpager-and-fragments-part-ii.html</a></p> <p>In short: you keep track of all the "active" fragment pages. In this case, you keep track of the fragment pages in the FragmentStatePagerAdapter, which is used by the ViewPager..</p> <pre><code>public Fragment getItem(int index) { Fragment myFragment = MyFragment.newInstance(); mPageReferenceMap.put(index, myFragment); return myFragment; } </code></pre> <p>To avoid keeping a reference to "inactive" fragment pages, we need to implement the FragmentStatePagerAdapter's destroyItem(...) method:</p> <pre><code>public void destroyItem(View container, int position, Object object) { super.destroyItem(container, position, object); mPageReferenceMap.remove(position); } </code></pre> <p>... and when you need to access the currently visible page, you then call:</p> <pre><code>int index = mViewPager.getCurrentItem(); MyAdapter adapter = ((MyAdapter)mViewPager.getAdapter()); MyFragment fragment = adapter.getFragment(index); </code></pre> <p>... where the MyAdapter's getFragment(int) method looks like this:</p> <pre><code>public MyFragment getFragment(int key) { return mPageReferenceMap.get(key); } </code></pre> <p>--- EDIT:</p> <p>Also add this in your adapter, for after an orientation change:</p> <pre><code>/** * After an orientation change, the fragments are saved in the adapter, and * I don't want to double save them: I will retrieve them and put them in my * list again here. */ @Override public Object instantiateItem(ViewGroup container, int position) { MyFragment fragment = (MyFragment) super.instantiateItem(container, position); mPageReferenceMap.put(position, fragment); return fragment; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAndroid FragmentStatePagerAdapter, how to tag a fragment to find it later
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFrank
    1. USFrank
    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. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGood call, second solution from that link is just what I needed for the FragmentStatePagerAdapter. I am just becoming familiar with the ViewPager API and was at a loss for how to keep track. This is the most straightforward way to think about it.
      singulars
      1. PO
      1. USicecreamman
    2. COI have used a solution like that too and was hoping that the link had something I hadn't done before :( Anyway, it's not bad, I just wish the Adapter would offer a mechanism to access the FragmentManager it uses internally.
      singulars
      1. PO
      1. USMartin Marconcini
    3. COThis does not work if the host activity is destroyed and re-created from the scratch. getItem(index) will not be called and your mPageReferenceMap will be empty. Go to developer options -> "Don't keep Activities" and see for yourself.
      singulars
      1. PO
      1. USAlexey
 

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