在ActivityThread中,当Activity被创建完毕后,会将DecorView添加到Window中,同时会创建ViewRootImpl对象,并将ViewRootImpl和DecorView建立关联。View的绘制流程是从ViewRoot的performTraversals方法开始,performTraversals会一次调用performMeasure、performLayout、performDraw三个方法,这三个方法分别完成顶级View的measure、layout、draw三个流程。其中measure确定View的测量宽高,layout确定View的最终宽高和四个顶点的位置,draw则将View绘制到屏幕上。
1.measure过程
measure过程要分情况,如果一个原始View,通过measure就完成了他的测量过程,如果是一个ViewGroup,除了完成自己的测量过程外,还会遍历去调用所有子元素的measure,各个子元素再递归去执行这个流程。
1)View的measure
View的measure方法是一个final类型的方法,表示子类不能重写此方法,在View的measure方法中会调用onMeasure,源码如下:
protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
setMeasuredDimension(getDefaultSize(getSuggestedMinimumWidth(),widthMeasureSpec),
getDefaultSize(getSuggestedMinimumHeight(), heightMeasureSpec));
}
setMeasuredDimension方法会设置View的宽高的测量值。
getDefaultSize方法源码:
public static int getDefaultSize(int size, int measureSpec) {
int result = size;
int specMode = MeasureSpec.getMode(measureSpec);
int specSize = MeasureSpec.getSize(measureSpec);
switch (specMode) {
case MeasureSpec.UNSPECIFIED:
result = size;
break;
case MeasureSpec.AT_MOST:
case MeasureSpec.EXACTLY:
result = specSize;
break;
}
return result;
}
可以看出,当传入的MeasureSpec的SpecMode为EXACTLY或者AT_MOST时,该方法返回的就是MeasureSpec的SpecSize,这个SpecSize就是View的测量宽高,View的最终大小是在Layout阶段确定的,但几乎所有情况下View的测量大小和最终大小是相等的。
当SpecMode为UNSPECIFIED时,getDefaultSize返回值是他的第一个参数size。即getSuggestedMinimumWidth和getSuggestedMinimumHeight的返回值,源码如下:
protected int getSuggestedMinimumWidth() {
return (mBackground == null) ? mMinWidth : max(mMinWidth, mBackground.getMinimumWidth());
}
protected int getSuggestedMinimumHeight() {
return (mBackground == null) ? mMinHeight : max(mMinHeight, mBackground.getMinimumHeight());
}
从源码可知,如果View没有设置背景,那么该方法的返回值是android:minWidth的值,该值默认为0,所以此时view的宽度就位android:minWidth的值。如果View指定了背景,那么View的宽度就为max(mMinWidth,mBackground.getMinimumWidth()),即android:width和背景的原始宽度中的较大值。mBackground是一个Drawable类对象,Drawable类中的getMinimumWidth方法源码如下:
public int getMinimumWidth() {
final int intrinsicWidth = getIntrinsicWidth();
return intrinsicWidth > 0 ? intrinsicWidth : 0;
}
2)ViewGroup的measure过程
对于ViewGroup来说除了完成自己的measure过程,还需要去遍历调用所有子元素的measure方法,各个子元素再去递归这个过程。和View不同的是,ViewGroup是一个抽象类,它没有重写View的onMeasure方法,当时他提供了一个measureChildren,源码如下:
protected void measureChildren(int widthMeasureSpec, int heightMeasureSpec) {
final int size = mChildrenCount;
final View[] children = mChildren;
for (int i = 0; i < size; ++i) {
final View child = children[i];
if ((child.mViewFlags & VISIBILITY_MASK) != GONE) {
measureChild(child, widthMeasureSpec, heightMeasureSpec);
}
}
}
ViewGroup在measureChildren方法中,会对每一个子元素进行measureChild,源码如下:
protected void measureChild(View child, int parentWidthMeasureSpec,int parentHeightMeasureSpec) {
final LayoutParams lp = child.getLayoutParams();
final int childWidthMeasureSpec = getChildMeasureSpec(parentWidthMeasureSpec,mPaddingLeft + mPaddingRight, lp.width);
final int childHeightMeasureSpec = getChildMeasureSpec(parentHeightMeasureSpec,mPaddingTop + mPaddingBottom, lp.height);
child.measure(childWidthMeasureSpec, childHeightMeasureSpec);
}
measureChild主要是取出子元素的layoutParams,然后通过getChildMeasureSpec,结合父元素的MeasureSpec、padding值以及子View本身的layoutParams来创建子元素的MeasureSpec,接着将MeasureSpec传递给子View的measure方法来进行子View的测量过程。
由于ViewGroup是一个抽象类,所以其测量的具体工程没有实现,需要各个子类去具体实现,比如LinearLayout,RelativeLayout等等,不同的ViewGroup子类具有不同的布局特性,测量细节各不相同。
2.layout过程
layout的作用是ViewGroup确定子元素的位置,当ViewGroup位置被确定后,会在onLayout中遍历所有子元素并调用子元素的layout方法,在layout中onLayout又会被调用。Layout方法确定View本身的位置,onLayout则会确定子元素的位置。View的layout方法源码:
public void layout(int l, int t, int r, int b) {
if ((mPrivateFlags3 & PFLAG3_MEASURE_NEEDED_BEFORE_LAYOUT) != 0) {
onMeasure(mOldWidthMeasureSpec, mOldHeightMeasureSpec);
mPrivateFlags3 &= ~PFLAG3_MEASURE_NEEDED_BEFORE_LAYOUT;
}
int oldL = mLeft;
int oldT = mTop;
int oldB = mBottom;
int oldR = mRight;
boolean changed = isLayoutModeOptical(mParent) ?
setOpticalFrame(l, t, r, b) : setFrame(l, t, r, b);
if (changed || (mPrivateFlags & PFLAG_LAYOUT_REQUIRED) == PFLAG_LAYOUT_REQUIRED) {
onLayout(changed, l, t, r, b);
if (shouldDrawRoundScrollbar()) {
if(mRoundScrollbarRenderer == null) {
mRoundScrollbarRenderer = new RoundScrollbarRenderer(this);
}
} else {
mRoundScrollbarRenderer = null;
}
mPrivateFlags &= ~PFLAG_LAYOUT_REQUIRED;
ListenerInfo li = mListenerInfo;
if (li != null && li.mOnLayoutChangeListeners != null) {
ArrayList<OnLayoutChangeListener> listenersCopy =
(ArrayList<OnLayoutChangeListener>)li.mOnLayoutChangeListeners.clone();
int numListeners = listenersCopy.size();
for (int i = 0; i < numListeners; ++i) {
listenersCopy.get(i).onLayoutChange(this, l, t, r, b, oldL, oldT, oldR, oldB);
}
}
}
mPrivateFlags &= ~PFLAG_FORCE_LAYOUT;
mPrivateFlags3 |= PFLAG3_IS_LAID_OUT;
if ((mPrivateFlags3 & PFLAG3_NOTIFY_AUTOFILL_ENTER_ON_LAYOUT) != 0) {
mPrivateFlags3 &= ~PFLAG3_NOTIFY_AUTOFILL_ENTER_ON_LAYOUT;
notifyEnterOrExitForAutoFillIfNeeded(true);
}
}
layout会调用setFrame方法来设定View的四个顶点的位置,即mLeft、mRight、mTop、mBottom四个值,四个顶点一旦确定,View在父容器中的位置就确定了,接着调用onLayout方法,用来确定子元素的位置,与onMeasure类似,onLayout同样和具体的布局有关,所以View和ViewGroup都没有具体实现。
3.draw过程
draw过程的作用是将View绘制到屏幕上,步骤如下:
1.绘制背景background.draw(canvas)
2.绘制自己(onDraw)
3.绘制children(dispatchDraw)
4.绘制装饰(onDrawScrollBars)
源码如下:
public void draw(Canvas canvas) {
final int privateFlags = mPrivateFlags;
final boolean dirtyOpaque = (privateFlags & PFLAG_DIRTY_MASK) == PFLAG_DIRTY_OPAQUE &&
(mAttachInfo == null || !mAttachInfo.mIgnoreDirtyState);
mPrivateFlags = (privateFlags & ~PFLAG_DIRTY_MASK) | PFLAG_DRAWN;
/*
* Draw traversal performs several drawing steps which must be executed
* in the appropriate order:
*
* 1. Draw the background
* 2. If necessary, save the canvas' layers to prepare for fading
* 3. Draw view's content
* 4. Draw children
* 5. If necessary, draw the fading edges and restore layers
* 6. Draw decorations (scrollbars for instance)
*/
// Step 1, draw the background, if needed
int saveCount;
if (!dirtyOpaque) {
drawBackground(canvas);
}
// skip step 2 & 5 if possible (common case)
final int viewFlags = mViewFlags;
boolean horizontalEdges = (viewFlags & FADING_EDGE_HORIZONTAL) != 0;
boolean verticalEdges = (viewFlags & FADING_EDGE_VERTICAL) != 0;
if (!verticalEdges && !horizontalEdges) {
// Step 3, draw the content
if (!dirtyOpaque) onDraw(canvas);
// Step 4, draw the children
dispatchDraw(canvas);
drawAutofilledHighlight(canvas);
// Overlay is part of the content and draws beneath Foreground
if (mOverlay != null && !mOverlay.isEmpty()) {
mOverlay.getOverlayView().dispatchDraw(canvas);
}
// Step 6, draw decorations (foreground, scrollbars)
onDrawForeground(canvas);
// Step 7, draw the default focus highlight
drawDefaultFocusHighlight(canvas);
if (debugDraw()) {
debugDrawFocus(canvas);
}
// we're done...
return;
}
...
}
View的绘制过程的传递是通过dispatchDraw来实现的,dispatchDraw会遍历调用所有的子元素的draw,如果draw就层层传递了下去,View有一个特殊的方法setWillNotDraw,源码如下:
/**
* If this view doesn't do any drawing on its own, set this flag to
* allow further optimizations. By default, this flag is not set on
* View, but could be set on some View subclasses such as ViewGroup.
*
* Typically, if you override {@link #onDraw(android.graphics.Canvas)}
* you should clear this flag.
*
* @param willNotDraw whether or not this View draw on its own
*/
public void setWillNotDraw(boolean willNotDraw) {
setFlags(willNotDraw ? WILL_NOT_DRAW : 0, DRAW_MASK);
}
如果一个View不需要绘制任何内容,那么将这个flag置为true,系统就会做相应的优化。默认情况下View没有启用优化标记位,但是ViewGroup是默认启用的。如果自定义控件继承自ViewGroup并且本身不具备绘制功能时,就可以开启标记位进行优化,如果需要通过ondraw进行绘制内容时,就要显式的关闭WILL_NOT_DRAW。