Window Activity View ViewRootImpl之间的关系理解

Window Activity View ViewRootImpl

window是一个抽象类，他的唯一实现类是PhoneWindow PhoneWindow的创建是在Activity的attch方法中

final void attach(Context context, ActivityThread aThread,
            Instrumentation instr, IBinder token, int ident,
            Application application, Intent intent, ActivityInfo info,
            CharSequence title, Activity parent, String id,
            NonConfigurationInstances lastNonConfigurationInstances,
            Configuration config, String referrer, IVoiceInteractor voiceInteractor,
            Window window) {
        attachBaseContext(context);

        mFragments.attachHost(null /*parent*/);

        mWindow = new PhoneWindow(this, window);
        mWindow.setWindowControllerCallback(this);
        mWindow.setCallback(this);
        mWindow.setOnWindowDismissedCallback(this);
        mWindow.getLayoutInflater().setPrivateFactory(this);
        if (info.softInputMode != WindowManager.LayoutParams.SOFT_INPUT_STATE_UNSPECIFIED) {
            mWindow.setSoftInputMode(info.softInputMode);
        }
        if (info.uiOptions != 0) {
            mWindow.setUiOptions(info.uiOptions);
        }
        
          mWindowManager = mWindow.getWindowManager();
    }
复制代码

所以每个activity都有一个phonewindow和mWindowManager

（WindowManager是一个接口并且继承ViewManager，里面有addView，updateViewLayout, removeView三大方法，WindowManager的实现类是WindowManagerImpl,在WindowManagerImpl中这三大方法的实现交由WindowManagerGlobal实现）

通过Activity的setContentView 方法为activity 设置布局时会调用window的setContentView方法。在这个方法中会生成DecorView并与当前window绑定

 private void installDecor() {
        mForceDecorInstall = false;
        if (mDecor == null) {
            mDecor = generateDecor(-1);
            mDecor.setDescendantFocusability(ViewGroup.FOCUS_AFTER_DESCENDANTS);
            mDecor.setIsRootNamespace(true);
            if (!mInvalidatePanelMenuPosted && mInvalidatePanelMenuFeatures != 0) {
                mDecor.postOnAnimation(mInvalidatePanelMenuRunnable);
            }
        } else {
            mDecor.setWindow(this);
        }
        if (mContentParent == null) {
            mContentParent = generateLayout(mDecor);//1
复制代码

注意在1处的代码，这里生成了mContentParent，继续进入生成mContentParent的generateLayout我们会发现，在这里设置activity的主题相关信息，这也就是为什么要在setContentView之前设置主题的原因了

protected ViewGroup generateLayout(DecorView decor) {
        // Apply data from current theme.

        TypedArray a = getWindowStyle();

        if (false) {
            System.out.println("From style:");
            String s = "Attrs:";
            for (int i = 0; i < R.styleable.Window.length; i++) {
                s = s + " " + Integer.toHexString(R.styleable.Window[i]) + "="
                        + a.getString(i);
            }
            System.out.println(s);
        }

        mIsFloating = a.getBoolean(R.styleable.Window_windowIsFloating, false);
        int flagsToUpdate = (FLAG_LAYOUT_IN_SCREEN|FLAG_LAYOUT_INSET_DECOR)
                & (~getForcedWindowFlags());
        if (mIsFloating) {
            setLayout(WRAP_CONTENT, WRAP_CONTENT);
            setFlags(0, flagsToUpdate);
        } else {
            setFlags(FLAG_LAYOUT_IN_SCREEN|FLAG_LAYOUT_INSET_DECOR, flagsToUpdate);
        }

        if (a.getBoolean(R.styleable.Window_windowNoTitle, false)) {
            requestFeature(FEATURE_NO_TITLE);
        } else if (a.getBoolean(R.styleable.Window_windowActionBar, false)) {
            requestFeature(FEATURE_ACTION_BAR);
        }

    .....
    
       ViewGroup contentParent = (ViewGroup)findViewById(ID_ANDROID_CONTENT);//1

复制代码

在1处的代码发现通过findViewById(ID_ANDROID_CONTENT)生成mContentParent，其中ID_ANDROID_CONTENT就是android.R.id.content,也就是通知栏以下的布局，这样DecorView就是activity的跟布局了。

在onResume中通过WindowManager.addView(decor)将布局展示出来。

接下来看下WindowManager addView方法

如上面分析的 WindowManager的实现类是WindowManagerImpl,而WindowManagerImpl内部通过WindowManagerGlobal实现view的添加。

public void addView(View view, ViewGroup.LayoutParams params,
            Display display, Window parentWindow) {
        if (view == null) {
            throw new IllegalArgumentException("view must not be null");
        }
        if (display == null) {
            throw new IllegalArgumentException("display must not be null");
        }
        if (!(params instanceof WindowManager.LayoutParams)) {
            throw new IllegalArgumentException("Params must be WindowManager.LayoutParams");
        }

        final WindowManager.LayoutParams wparams = (WindowManager.LayoutParams) params;
        if (parentWindow != null) {
            parentWindow.adjustLayoutParamsForSubWindow(wparams);
        } else {
            // If there's no parent, then hardware acceleration for this view is
            // set from the application's hardware acceleration setting.
            final Context context = view.getContext();
            if (context != null
                    && (context.getApplicationInfo().flags
                            & ApplicationInfo.FLAG_HARDWARE_ACCELERATED) != 0) {
                wparams.flags |= WindowManager.LayoutParams.FLAG_HARDWARE_ACCELERATED;
            }
        }

        ViewRootImpl root;
        View panelParentView = null;

        synchronized (mLock) {
            // Start watching for system property changes.
            if (mSystemPropertyUpdater == null) {
                mSystemPropertyUpdater = new Runnable() {
                    @Override public void run() {
                        synchronized (mLock) {
                            for (int i = mRoots.size() - 1; i >= 0; --i) {
                                mRoots.get(i).loadSystemProperties();
                            }
                        }
                    }
                };
                SystemProperties.addChangeCallback(mSystemPropertyUpdater);
            }
            
            root = new ViewRootImpl(view.getContext(), display);//1

            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);//2
        } catch (RuntimeException e) {
            // BadTokenException or InvalidDisplayException, clean up.
            synchronized (mLock) {
                final int index = findViewLocked(view, false);
                if (index >= 0) {
                    removeViewLocked(index, true);
                }
            }
            throw e;
        }
    }
复制代码

可以看到在1处创建了ViewRootImpl,WindowManagerGlobal内部维护了三个数组用于存放添加的view、ViewRootImpl、WindowManager.LayoutParams和将要移除的view。

 private final ArrayList<View> mViews = new ArrayList<View>();
    private final ArrayList<ViewRootImpl> mRoots = new ArrayList<ViewRootImpl>();
    private final ArrayList<WindowManager.LayoutParams> mParams =
            new ArrayList<WindowManager.LayoutParams>();
    private final ArraySet<View> mDyingViews = new ArraySet<View>();
复制代码

最后在代码2处调用 root.setView(view, wparams, panelParentView)，然后在该方法内部调用requestLayout执行view的三大流程。随后会通过Binder对象WindowSession将Window的添加请求发送给WindowManagerService。

总结：每个Activity对应一个PhoneWindow,window与decorView相关联。设置布局的时候使用WindowManager addView,每调用一次addView便创建一个ViewRootImpl,也就是创建一颗view树。

转载于:https://juejin.im/post/5ba0bec25188255c9e02c732