自定義View是Android開發中最普通的需求,靈活控制View的尺寸是開發者面臨的第一個問題,比如,為什麼明明使用的是WRAP_CONTENT卻跟MATCH_PARENT表現相同。在處理View尺寸的時候,我們都知道最好在onMeasure中設定好自定義View尺寸,那麼究竟如何合理的選擇這個尺寸呢。直觀來說,可能有以下問題需要考慮:
以上三個問題可能是自定義ViewGroup最需要考慮的問題,首先先解決第一個問題。
先假定,父容器是300dp*300dp的尺寸,如果子View的布局參數是
<!--場景1-->android:layout_width="match_parent"android:layout_height="match_parent"
那麼按照我們的期望,希望子View的尺寸要是300dp*300dp,如果子View的布局參數是
<!--場景2-->android:layout_width="100dp"android:layout_height="100dp"
按照我們的期望,希望子View的尺寸要是100dp*100dp,如果子View的布局參數是
<!--場景3-->android:layout_width="wrap_content"android:layout_height="wrap_content"
按照我們的期望,希望子View的尺寸可以按照自己需求的尺寸來確定,但是最好不要超過300dp*300dp。
那麼父容器怎麼把這些要求告訴子View呢?MeasureSpec其實就是承擔這種作用:MeasureSpec是父控制項提供給子View的一個參數,作為設定自身大小參考,只是個參考,要多大,還是View自己說了算。先看下MeasureSpec的構成,MeasureSpec由size和mode組成,mode包括三種,UNSPECIFIED、EXACTLY、AT_MOST,size就是配合mode給出的參考尺寸,具體意義如下:
先來看一下ViewGroup源碼中measureChild怎麼為子View構造MeasureSpec的:
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); }
由於任何View都是支持Padding參數的,在為子View設置參考尺寸的時候,需要先把自己的Padding給去除,這同時也是為了Layout做鋪墊。接著看如何getChildMeasureSpec獲取傳遞給子View的MeasureSpec的:
public static int getChildMeasureSpec(int spec, int padding, int childDimension) { int specMode = MeasureSpec.getMode(spec); int specSize = MeasureSpec.getSize(spec); int size = Math.max(0, specSize - padding); int resultSize = 0; int resultMode = 0; switch (specMode) { // Parent has imposed an exact size on us case MeasureSpec.EXACTLY: if (childDimension >= 0) { resultSize = childDimension; resultMode = MeasureSpec.EXACTLY; } else if (childDimension == LayoutParams.MATCH_PARENT) { // Child wants to be our size. So be it. resultSize = size; resultMode = MeasureSpec.EXACTLY; } else if (childDimension == LayoutParams.WRAP_CONTENT) { // Child wants to determine its own size. It can't be // bigger than us. resultSize = size; resultMode = MeasureSpec.AT_MOST; } break; // Parent has imposed a maximum size on us case MeasureSpec.AT_MOST: if (childDimension >= 0) { // Child wants a specific size... so be it resultSize = childDimension; resultMode = MeasureSpec.EXACTLY; } else if (childDimension == LayoutParams.MATCH_PARENT) { // Child wants to be our size, but our size is not fixed. // Constrain child to not be bigger than us. resultSize = size; resultMode = MeasureSpec.AT_MOST; } else if (childDimension == LayoutParams.WRAP_CONTENT) { // Child wants to determine its own size. It can't be // bigger than us. resultSize = size; resultMode = MeasureSpec.AT_MOST; } break; // Parent asked to see how big we want to be case MeasureSpec.UNSPECIFIED: if (childDimension >= 0) { // Child wants a specific size... let him have it resultSize = childDimension; resultMode = MeasureSpec.EXACTLY; } else if (childDimension == LayoutParams.MATCH_PARENT) { // Child wants to be our size... find out how big it should // be resultSize = View.sUseZeroUnspecifiedMeasureSpec ? 0 : size; resultMode = MeasureSpec.UNSPECIFIED; } else if (childDimension == LayoutParams.WRAP_CONTENT) { // Child wants to determine its own size.... find out how // big it should be resultSize = View.sUseZeroUnspecifiedMeasureSpec ? 0 : size; resultMode = MeasureSpec.UNSPECIFIED; } break; } return MeasureSpec.makeMeasureSpec(resultSize, resultMode);}
可以看到父控制項會參考自己的MeasureSpec跟子View的布局參數,為子View構建合適的MeasureSpec,盜用網上的一張圖來描述就是
當子View接收到父控制項傳遞的MeasureSpec的時候,就可以知道父控制項希望自己如何顯示,這個點對於開發者而言就是onMeasure函數,先來看下View.java中onMeasure函數的實現:
protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) { setMeasuredDimension(getDefaultSize(getSuggestedMinimumWidth(), widthMeasureSpec), getDefaultSize(getSuggestedMinimumHeight(), heightMeasureSpec));}
其中getSuggestedMinimumWidth是根據設置的背景跟最小尺寸得到一個備用的參考尺寸,接著看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;}
可以看到,如果自定義View沒有重寫onMeasure函數,MeasureSpec.AT_MOST跟MeasureSpec.AT_MOST的表現是一樣的,也就是對於場景2跟3的表現其實是一樣的,也就是wrap_content就跟match_parent一個效果,現在我們知道MeasureSpec的主要作用:父控制項傳遞給子View的參考,那么子View拿到後該如何用呢?
自定義View尺寸的確定
接收到父控制項傳遞的MeasureSpec後,View應該如何用來處理自己的尺寸呢?onMeasure是View測量尺寸最合理的時機,如果View不是ViewGroup相對就比較簡單,只需要參照MeasureSpec,並跟自身需求來設定尺寸即可,默認onMeasure的就是完全按照父控制項傳遞MeasureSpec設定自己的尺寸的。這裡重點講一下ViewGroup,為了獲得合理的寬高尺寸,ViewGroup在計算自己尺寸的時候,必須預先知道所有子View的尺寸,舉個例子,用一個常用的流式布局FlowLayout來講解一下如何合理的設定自己的尺寸。
先分析一下FLowLayout流式布局(從左到右)的特點:FLowLayout將所有子View從左往右依次放置,如果當前行,放不開的就換行。從流失布局的特點來看,在確定FLowLayout尺寸的時候,我們需要知道下列信息,
首先看父容器傳遞給FlowLayout的MeasureSpec,對開發者而言,它可見於onMeasure函數,是通過onMeasure的參數傳遞進來的,它的意義上面的已經說過了,現在來看,怎麼用比較合理?其實ViewGroup.java源碼中也提供了比較簡潔的方法,有兩個比較常用的measureChildren跟resolveSize,在之前的分析中我們知道measureChildren會調用getChildMeasureSpec為子View創建MeasureSpec,並通過measureChild測量每個子View的尺寸。那麼resolveSize呢,看下面源碼,resolveSize(int size, int measureSpec)的兩個輸入參數,第一個參數:size,是View自身希望獲取的尺寸,第二參數:measureSpec,其實父控制項傳遞給View,推薦View獲取的尺寸,resolveSize就是綜合考量兩個參數,最後給一個建議的尺寸:
public static int resolveSize(int size, int measureSpec) { return resolveSizeAndState(size, measureSpec, 0) & MEASURED_SIZE_MASK; }public static int resolveSizeAndState(int size, int measureSpec, int childMeasuredState) { final int specMode = MeasureSpec.getMode(measureSpec); final int specSize = MeasureSpec.getSize(measureSpec); final int result; switch (specMode) { case MeasureSpec.AT_MOST: if (specSize < size) { result = specSize | MEASURED_STATE_TOO_SMALL; } else { result = size; } break; case MeasureSpec.EXACTLY: result = specSize; break; case MeasureSpec.UNSPECIFIED: default: result = size; } return result | (childMeasuredState & MEASURED_STATE_MASK);}
可以看到:
對於FlowLayout,可以假設每個子View都可以充滿FlowLayout,因此,可以直接用measureChildren測量所有的子View的尺寸:
@Overrideprotected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) { int widthSize = MeasureSpec.getSize(widthMeasureSpec); int paddingLeft = getPaddingLeft(); int paddingRight = getPaddingRight(); int paddingBottom = getPaddingBottom(); int paddingTop = getPaddingTop(); int count = getChildCount(); int maxWidth = 0; int totalHeight = 0; int lineWidth = 0; int lineHeight = 0; int extraWidth = widthSize - paddingLeft - paddingRight; <!--直接用measureChildren測量所有的子View的高度--> measureChildren(widthMeasureSpec, heightMeasureSpec); <!--現在可以獲得所有子View的尺寸--> for (int i = 0; i < count; i++) { View view = getChildAt(i); if (view != null && view.getVisibility() != GONE) { if (lineWidth + view.getMeasuredWidth() > extraWidth) { totalHeight += lineHeight ; lineWidth = view.getMeasuredWidth(); lineHeight = view.getMeasuredHeight(); maxWidth = widthSize; } else { lineWidth += view.getMeasuredWidth(); } <!--獲取每行的最高View尺寸--> lineHeight = Math.max(lineHeight, view.getMeasuredHeight()); } } totalHeight = Math.max(totalHeight + lineHeight, lineHeight); maxWidth = Math.max(lineWidth, maxWidth); <!--totalHeight 跟 maxWidth都是FlowLayout渴望得到的尺寸--> <!--至於合不合適,通過resolveSize再來判斷一遍,當然,如果你非要按照自己的尺寸來,也可以設定,但是不太合理--> totalHeight = resolveSize(totalHeight + paddingBottom + paddingTop, heightMeasureSpec); lineWidth = resolveSize(maxWidth + paddingLeft + paddingRight, widthMeasureSpec); setMeasuredDimension(lineWidth, totalHeight);}
可以看到,設定自定義ViewGroup的尺寸其實只需要三部:
傳遞給子View的MeasureSpec是父容器根據自己的MeasureSpec及子View的布局參數所確定的,那麼根MeasureSpec是誰創建的呢?我們用最常用的兩種Window來解釋一下,Activity與Dialog,DecorView是Activity的根布局,傳遞給DecorView的MeasureSpec是系統根據Activity或者Dialog的Theme來確定的,也就是說,最初的MeasureSpec是直接根據Window的屬性構建的,一般對於Activity來說,根MeasureSpec是EXACTLY+屏幕尺寸,對於Dialog來說,如果不做特殊設定會採用AT_MOST+屏幕尺寸。這裡牽扯到WindowManagerService跟ActivityManagerService,感興趣的可以跟蹤一下WindowManager.LayoutParams ,後面也會專門分析一下,比如,實現最簡單試的全屏的Dialog就跟這些知識相關。
作者:看書的小蝸牛
連結:https://www.jianshu.com/p/d16ec64181f2