Note that there are some explanatory texts on larger screens.

plurals
  1. POinitLoader one after another in Fragment
    primarykey
    data
    text
    <p>I have a fragment that need to loader 7 loaders </p> <p>in the onActivityCreate(); </p> <p>i call initLoader for all of them .</p> <pre><code>public void onActivityCreate(Bundle saveInstanceState){ LoaderManager mgr = getLoaderManager(); mgr.initLoader(0,null,mLoaderCallback0); mgr.initLoader(1,null,mLoaderCallback1); mgr.initLoader(2,null,mLoaderCallback2); mgr.initLoader(3,null,mLoaderCallback3); mgr.initLoader(4,null,mLoaderCallback4); mgr.initLoader(5,null,mLoaderCallback5); mgr.initLoader(6,null,mLoaderCallback6); } </code></pre> <p>how can i load them efficiently one by one for memory concerns ,</p> <p>What i was thinking about </p> <p>is to loader the first loader in <code>onActivityCreated</code> method and inside the <code>onLoadFinished</code> of it callback i load the second loader and in the second <code>onLoadFinished</code> i <code>initLoader</code> the third and so on. is it good ? or i miss something regards to fragment life cycle.</p> <pre><code> private LoaderCallbacks&lt;UserFriendResponse&gt; mFirstCallbacks = new LoaderCallbacks&lt;UserFriendResponse&gt;() { @Override public void onLoaderReset(Loader&lt;UserFriendResponse&gt; arg0) { // TODO Auto-generated method stub } @Override public void onLoadFinished(Loader&lt;Type1&gt; arg0, Type1 arg1) { .... ... .. if(isAdded()){ getLoaderManager().initLoader(1,null,mLoaderCallback1); } } @Override public Loader&lt;Type1&gt; onCreateLoader(int arg0, Bundle arg1) { return new CustomLoader(getActivity(), false, true, false, "1", 1, username); } }; </code></pre> <p><strong>Note : i can't have one callback because each loader return different data type .</strong> </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

Querying!

 
Guidance

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