上一篇主要理了下LoaderCallback, 其中看到LoaderManager在initLoader之后自動調用了Loader的startLoading方法； 這一篇繼續(xù)理Loader !最后我們就可以把Loader執(zhí)行過程的整個生命周期畫出來了。

先看結構吧，Loader簡單多了。

該類源碼查看：http://www.oschina.net/code/explore/android-4.0.1/core/java/android/content/Loader.java

首先是startLoading 方法

        public final void startLoading() {
        mStarted = true;
        mReset = false;
        mAbandoned = false;
        onStartLoading();
    }

    /***
     * Subclasses must implement this to take care of loading their data,
     * as per {@link #startLoading()}.  This is not called by clients directly,
     * but as a result of a call to {@link #startLoading()}.
     */
    protected void onStartLoading() {
    }
  

看到?jīng)]，設置了幾個狀態(tài), 然后調用onStartLoading方法就結束了, 而onStartLoading方法又是個空方法.. 好了，圓滿結束!....

尼瑪, 難怪我的loadInBackground方法總是不被調用! 坑爹啊! 那怎么讓你自己Loader的loadInBackground正常被調用呢? 只能重寫onStartLoading方法唄！

看看官方的示例（http://developer.android.com/intl/zh-CN/reference/android/content/AsyncTaskLoader.html）：

        /**
     * Handles a request to start the Loader.
     */
    @Override protected void onStartLoading() {
        if (mApps != null) {
            // If we currently have a result available, deliver it
            // immediately.
            deliverResult(mApps);
        }

        // Start watching for changes in the app data.
        if (mPackageObserver == null) {
            mPackageObserver = new PackageIntentReceiver(this);
        }

        // Has something interesting in the configuration changed since we
        // last built the app list?
        boolean configChange = mLastConfig.applyNewConfig(getContext().getResources());

        if (takeContentChanged() || mApps == null || configChange) {
            // If the data has changed since the last time it was loaded
            // or is not currently available, start a load.
            forceLoad();
        }
    }
  

有事.. 先到這..

[Loader] 從startLoading()說開去..