Android界面绘制原理

Android的Activity界面从何处开始绘制

• Activity启动之后，灰溜溜的会去跑onCreate，onStart，onResume等生命周期方法，那么从framework里面，让我们看看Activity在onResume之前都在干些啥？ 在ActivityThread中的handleResumeActivity方法中先调用了performResumeActivity方法，而performResumeActivity中就会去回调Activity中的onResume方法，在performResumeActivity后，又做了很多事，所以如果在onResume中去做一些耗时操作是无法加速页面启动的，因为这时候页面还没展示出来呢，这里额外提一句，接着唠，performResumeActivity执行完了之后

if (r.window == null && !a.mFinished && willBeVisible) {
                r.window = r.activity.getWindow();
                View decor = r.window.getDecorView();
                decor.setVisibility(View.INVISIBLE);
                ViewManager wm = a.getWindowManager();
                WindowManager.LayoutParams l = r.window.getAttributes();
                a.mDecor = decor;
                l.type = WindowManager.LayoutParams.TYPE_BASE_APPLICATION;
                l.softInputMode |= forwardBit;
                if (r.mPreserveWindow) {
                    a.mWindowAdded = true;
                    r.mPreserveWindow = false;
                    // Normally the ViewRoot sets up callbacks with the Activity
                    // in addView->ViewRootImpl#setView. If we are instead reusing
                    // the decor view we have to notify the view root that the
                    // callbacks may have changed.
                    ViewRootImpl impl = decor.getViewRootImpl();
                    if (impl != null) {
                        impl.notifyChildRebuilt();
                    }
                }
                if (a.mVisibleFromClient) {
                    if (!a.mWindowAdded) {
                        a.mWindowAdded = true;
                        wm.addView(decor, l);
                    } else {
                        // The activity will get a callback for this {@link LayoutParams} change
                        // earlier. However, at that time the decor will not be set (this is set
                        // in this method), so no action will be taken. This call ensures the
                        // callback occurs with the decor set.
                        a.onWindowAttributesChanged(l);
                    }
                }

            // If the window has already been added, but during resume
            // we started another activity, then don't yet make the
            // window visible.
            }

从普遍的意义上来讲，以上这段代码就是设置WindowManager和DecorView的关系，继续看：

if (a.mVisibleFromClient) {
                    if (!a.mWindowAdded) {
                        a.mWindowAdded = true;
                        wm.addView(decor, l);
                    } else {
                        // The activity will get a callback for this {@link LayoutParams} change
                        // earlier. However, at that time the decor will not be set (this is set
                        // in this method), so no action will be taken. This call ensures the
                        // callback occurs with the decor set.
                        a.onWindowAttributesChanged(l);
                    }
                }

wm.addView(decor, l)这句就是把DecorView加入到WindowManager当中，那么WindowManager是什么东西呢？在这句代码打了一个断点，然后层层跟进来，WindowManagerImpl：

public void addView(@NonNull View view, @NonNull ViewGroup.LayoutParams params) {
        applyDefaultToken(params);
        mGlobal.addView(view, params, mContext.getDisplay(), mParentWindow);
    }

再继续执行了WindowManagerGlobal的addView，此时addView中第一个参数View就是DecorView，由于代码太长，只贴关键部分：

root = new ViewRootImpl(view.getContext(), display);

            view.setLayoutParams(wparams);

            mViews.add(view);
            mRoots.add(root);
            mParams.add(wparams);

            // do this last because it fires off messages to start doing things
            try {
                root.setView(view, wparams, panelParentView);
            } catch (RuntimeException e) {
                // BadTokenException or InvalidDisplayException, clean up.
                if (index >= 0) {
                    removeViewLocked(index, true);
                }
                throw e;
            }

这里创建了一个ViewRootImpl对象root，然后调用root的setView方法，这个方法也太长，但是我可以负责任的告诉你，setView方法中调用了requestLayout()方法：

@Override
    public void requestLayout() {
        if (!mHandlingLayoutInLayoutRequest) {
            checkThread();
            mLayoutRequested = true;
            scheduleTraversals();
        }
    }

到这里，好了，界面绘制从这里开始：

void checkThread() {
        if (mThread != Thread.currentThread()) {
            throw new CalledFromWrongThreadException(
                    "Only the original thread that created a view hierarchy can touch its views.");
        }
    }

这个异常是不是经常碰到？这里就是要求界面绘制必须在主线程中进行更新mThread就是主线程，所以如果当前运行的线程不是主线程，那么就直接报这个异常，接下去是mLayoutRequested设置成true，避免在界面又layout请求的时候又重复收到一次layout请求，然后再进行界面的layout，那不就乱套了，然后就是真正的界面绘制了：

void scheduleTraversals() {
        if (!mTraversalScheduled) {
            mTraversalScheduled = true;
            mTraversalBarrier = mHandler.getLooper().getQueue().postSyncBarrier();
            mChoreographer.postCallback(
                    Choreographer.CALLBACK_TRAVERSAL, mTraversalRunnable, null);
            if (!mUnbufferedInputDispatch) {
                scheduleConsumeBatchedInput();
            }
            notifyRendererOfFramePending();
            pokeDrawLockIfNeeded();
        }
    }

核心在这里：

mChoreographer.postCallback(
                    Choreographer.CALLBACK_TRAVERSAL, mTraversalRunnable, null);

调用了Choreographer中的方法，方法中的mTraversalRunnable如下：

final class Travers