上一篇分析到了KeyEvent的分發(fā)其實(shí)就是把事件交給了焦點(diǎn)View處理,那怎么去定義一個(gè)View可獲得焦點(diǎn)?其實(shí)很簡(jiǎn)單,只需要在xml布局中設(shè)置View的focusable屬性為true就可以了,那現(xiàn)在就開始分析這個(gè)focusable屬性究竟是怎么發(fā)揮它的作用的。
View的焦點(diǎn)模式
View定義了三種焦點(diǎn)模式,直接看它們?cè)诖a中定義:
/**
* This view does not want keystrokes.
*/
public static final int NOT_FOCUSABLE = 0x00000000;
/**
* This view wants keystrokes.
*/
public static final int FOCUSABLE = 0x00000001;
/**
* This view determines focusability automatically. This is the default.
*/
public static final int FOCUSABLE_AUTO = 0x00000010;
/**
* Mask for use with setFlags indicating bits used for focus.
*/
private static final int FOCUSABLE_MASK = 0x00000011;
/**
* The view flags hold various views states.
* {@hide}
*/
@ViewDebug.ExportedProperty(formatToHexString = true)
int mViewFlags;
其中FOCUSABLE_MASK表示foucsable屬性占用mViewFlags的bit位置,可以看出mViewFlags中第1位和第5位用來(lái)聯(lián)合表示view的焦點(diǎn)模式,有FOCUSABLE、NOT_FOCUSABLE和FOCUSABLE_AUTO三種焦點(diǎn)模式,第1位控制FOCUSABLE、NOT_FOCUSABLE,第5位單獨(dú)控制FOCUSABLE_AUTO.
接著看看View的構(gòu)造方法中解析xml布局設(shè)置的focusable屬性的過程,主要的代碼如下:
View的構(gòu)造方法中
public View(Context context, @Nullable AttributeSet attrs,
int defStyleAttr, int defStyleRes) {
//設(shè)置默認(rèn)的值
mViewFlags = FOCUSABLE_AUTO;
// Set default values.
viewFlagValues |= FOCUSABLE_AUTO;
viewFlagMasks |= FOCUSABLE_AUTO;
......
for (int i = 0; i < N; i++) {
//獲取xml文件中設(shè)置的的焦點(diǎn)狀態(tài)
case com.android.internal.R.styleable.View_focusable:
// (viewFlagValues & ~FOCUSABLE_MASK) 將焦點(diǎn)狀態(tài)置為空,“與|”將從xml中獲取的焦點(diǎn)狀態(tài)賦值給viewFlagValues
viewFlagValues = (viewFlagValues & ~FOCUSABLE_MASK) | getFocusableAttribute(a);
//如果viewFlagValues中的焦點(diǎn)狀態(tài)不再是FOCUSABLE_AUTO,說(shuō)明焦點(diǎn)狀態(tài)變了,修改位變化記錄mask值
if ((viewFlagValues & FOCUSABLE_AUTO) == 0) {
viewFlagMasks |= FOCUSABLE_MASK;
}
break;
}
.......
if (viewFlagMasks != 0) {
setFlags(viewFlagValues, viewFlagMasks);
}
}
//將xml中設(shè)置的焦點(diǎn)狀態(tài)轉(zhuǎn)換為View自己定義的二進(jìn)制格式
private int getFocusableAttribute(TypedArray attributes) {
TypedValue val = new TypedValue();
if (attributes.getValue(com.android.internal.R.styleable.View_focusable, val)) {
if (val.type == TypedValue.TYPE_INT_BOOLEAN) {
return (val.data == 0 ? NOT_FOCUSABLE : FOCUSABLE);
} else {
return val.data;
}
} else {
return FOCUSABLE_AUTO;
}
}
在最開始的時(shí)候設(shè)置了View的焦點(diǎn)模式為FOCUSABLE_AUTO,在遍歷屬性時(shí)如果xml布局有設(shè)置focusable屬性,則取出,沒有的話依然是FOCUSABLE_AUTO,這樣focuable屬性就轉(zhuǎn)換成了viewFlagValues中的參數(shù),構(gòu)造方法最后還調(diào)用了setFlags方法設(shè)置mViewFlags,這個(gè)方法內(nèi)還處理設(shè)置了clickable但沒有設(shè)置focusable的情況,如下:
View中
void setFlags(int flags, int mask) {
//將flags變化了的bit同步到全局變量mViewFlags中
mViewFlags = (mViewFlags & ~mask) | (flags & mask);
......
// If focusable is auto, update the FOCUSABLE bit.
int focusableChangedByAuto = 0;
//焦點(diǎn)狀態(tài)是FOCUSABLE_AUTO
if (((mViewFlags & FOCUSABLE_AUTO) != 0)
&& (changed & (FOCUSABLE_MASK | CLICKABLE)) != 0) {
// Heuristic only takes into account whether view is clickable.
final int newFocus;
//View可以被點(diǎn)擊,將焦點(diǎn)狀態(tài)添加FOCUSABLE,否則添加NOT_FOCUSABLE
if ((mViewFlags & CLICKABLE) != 0) {
newFocus = FOCUSABLE;
} else {
newFocus = NOT_FOCUSABLE;
}
mViewFlags = (mViewFlags & ~FOCUSABLE) | newFocus;
.....
}
}
可以看出,如果是FOCUSABLE_AUTO情況,也就是xml文件沒設(shè)置focusable屬性,焦點(diǎn)的模式還與clickable屬性有關(guān),如果View是clickable的,那么View是FOCUSABLE,否則是NOT_FOCUSABLE,可以用下面這張表來(lái)描述clickable和focusable屬性對(duì)View的焦點(diǎn)模式的影響

現(xiàn)在可以回答上一篇結(jié)束時(shí)提的問題了,Android手機(jī)應(yīng)用運(yùn)行在Android電視上可以響應(yīng)按鍵事件嗎?如果這個(gè)View在xml文件中設(shè)置了clickable屬性為true那這個(gè)View就可以獲得焦點(diǎn),也就可以響應(yīng)按鍵事件,如果既沒有設(shè)置clickable也沒有設(shè)置focusable為true,那這個(gè)View就獲取不到焦點(diǎn),也就響應(yīng)不了按鍵事件了。
下面是View提供的兩種獲得焦點(diǎn)模式的方法
View中
public int getFocusable() {
//只要設(shè)置了FOCUSABLE_AUTO就只返回FOCUSABLE_AUTO
return (mViewFlags & FOCUSABLE_AUTO) > 0 ? FOCUSABLE_AUTO : mViewFlags & FOCUSABLE;
}
public final boolean isFocusable() {
return FOCUSABLE == (mViewFlags & FOCUSABLE);
}
一般情況我們使用isFocusable方法就OK了,getFocusable方法可以用來(lái)在可以獲得焦點(diǎn)時(shí)判斷是clickable導(dǎo)致的,還是focusable設(shè)置的.
ViewGroup的焦點(diǎn)模式
上小節(jié)分析的View的焦點(diǎn)模式完全適用于ViewGroup,畢竟它也是View的兒子,但由于ViewGroup有子View,為了避免焦點(diǎn)產(chǎn)生歧義,還定義了ViewGroup相對(duì)于子View的三種獲得焦點(diǎn)的順序,如下:
/**
在所有子View之前
* This view will get focus before any of its descendants.
*/
public static final int FOCUS_BEFORE_DESCENDANTS = 0x20000;
/**
在所有子View之后
* This view will get focus only if none of its descendants want it.
*/
public static final int FOCUS_AFTER_DESCENDANTS = 0x40000;
/**
攔截所有焦點(diǎn),不通知子View
* This view will block any of its descendants from getting focus, even
* if they are focusable.
*/
public static final int FOCUS_BLOCK_DESCENDANTS = 0x60000;
//定義mGroupFlags中的第17和18位用來(lái)表示這個(gè)順序
private static final int FLAG_MASK_FOCUSABILITY = 0x60000;
protected int mGroupFlags;
ViewGroup的FLAG_MASK_FOCUSABILITY是用來(lái)控制焦點(diǎn)在View樹中的傳遞順序的,順序有三種:
- FOCUS_BEFORE_DESCENDANTS: 在所有子View之前,自己沒獲取再給子View
- FOCUS_AFTER_DESCENDANTS: 在所有子View之后,所有子View都沒能獲得焦點(diǎn)才問下自己能不能
- FOCUS_BLOCK_DESCENDANTS: 不通知子View ,即使自己獲取不到
和View的焦點(diǎn)模式一樣,獲得焦點(diǎn)的順序也是在構(gòu)造方法中設(shè)置的:
ViewGroup中
private static final int[] DESCENDANT_FOCUSABILITY_FLAGS =
{FOCUS_BEFORE_DESCENDANTS, FOCUS_AFTER_DESCENDANTS,
FOCUS_BLOCK_DESCENDANTS};
public ViewGroup(Context context, AttributeSet attrs, int defStyleAttr, int defStyleRes) {
......
case R.styleable.ViewGroup_descendantFocusability:
//默認(rèn)是FOCUS_BEFORE_DESCENDANTS
setDescendantFocusability(DESCENDANT_FOCUSABILITY_FLAGS[a.getInt(attr, 0)]);
break;
}
public void setDescendantFocusability(int focusability) {
switch (focusability) {
case FOCUS_BEFORE_DESCENDANTS:
case FOCUS_AFTER_DESCENDANTS:
case FOCUS_BLOCK_DESCENDANTS:
break;
default:
throw new IllegalArgumentException("must be one of FOCUS_BEFORE_DESCENDANTS, "
+ "FOCUS_AFTER_DESCENDANTS, FOCUS_BLOCK_DESCENDANTS");
}
//設(shè)置順序
mGroupFlags &= ~FLAG_MASK_FOCUSABILITY;
mGroupFlags |= (focusability & FLAG_MASK_FOCUSABILITY);
}
從代碼中可以發(fā)現(xiàn),如果不寫這個(gè)屬性,ViewGroup設(shè)置自己在所有子View之前處理焦點(diǎn).
View的requestFocus方法
要讓一個(gè)View獲得焦點(diǎn),需要調(diào)用它的requestFocus方法,調(diào)用時(shí)序圖如下(具體的方法可以直接搜索源碼):

View先調(diào)用自己的canTakeFocus方法確認(rèn)自己是不是能夠獲得焦點(diǎn),這個(gè)方法如下:
private boolean canTakeFocus() {
return ((mViewFlags & VISIBILITY_MASK) == VISIBLE)
&& ((mViewFlags & FOCUSABLE) == FOCUSABLE)
&& ((mViewFlags & ENABLED_MASK) == ENABLED)
&& (sCanFocusZeroSized || !isLayoutValid() || hasSize());
}
判斷的依據(jù)是 : 1.view可見 2.可以獲得焦點(diǎn) 3.是enable的 4.有大小
然后遞歸調(diào)用所有父View的hasAncestorThatBlocksDescendantFocus方法,確認(rèn)父View是不是設(shè)置了攔截焦點(diǎn),如果父View攔截了焦點(diǎn),自己就不能獲得焦點(diǎn)。
如果上面兩項(xiàng)都通過了,那就可以名正言順的獲得焦點(diǎn)了,handleFocusGainInternal方法如下:
void handleFocusGainInternal(@FocusRealDirection int direction, Rect previouslyFocusedRect) {
if (DBG) {
System.out.println(this + " requestFocus()");
}
//修改狀態(tài),flag添加PFLAG_FOCUSED,標(biāo)記自己有焦點(diǎn)
if ((mPrivateFlags & PFLAG_FOCUSED) == 0) {
mPrivateFlags |= PFLAG_FOCUSED;
View oldFocus = (mAttachInfo != null) ? getRootView().findFocus() : null;
if (mParent != null) {
//通知父View,我現(xiàn)在是那個(gè)有焦點(diǎn)的View
mParent.requestChildFocus(this, this);
updateFocusedInCluster(oldFocus, direction);
}
//調(diào)用設(shè)置的View樹全局焦點(diǎn)變化監(jiān)聽
if (mAttachInfo != null) {
mAttachInfo.mTreeObserver.dispatchOnGlobalFocusChange(oldFocus, this);
}
//調(diào)用自己的onFocusChangeListener方法
onFocusChanged(true, direction, previouslyFocusedRect);
refreshDrawableState();
}
}
方法中將mPrivateFlags中的表示是否有焦點(diǎn)的bit置為1,表示自己有焦點(diǎn),這在上一章中分析過,之后調(diào)用父View的requestChildFocus的方法,如下:
@Override
public void requestChildFocus(View child, View focused) {
......
if (getDescendantFocusability() == FOCUS_BLOCK_DESCENDANTS) {
return;
}
// Unfocus us, if necessary
super.unFocus(focused);
// We had a previous notion of who had focus. Clear it.
if (mFocused != child) {
if (mFocused != null) {
mFocused.unFocus(focused);
}
//修改mFocused變量,指向這個(gè)新的獲得焦點(diǎn)的子View
mFocused = child;
}
if (mParent != null) {
//告訴父View,我是那個(gè)包含焦點(diǎn)View的乖兒子
mParent.requestChildFocus(this, focused);
}
父View的requestChildFocus方法中將mFocused成員變量指向這個(gè)有焦點(diǎn)的View,然后通知自己的父View我是那個(gè)包含焦點(diǎn)View的子View,如此遍歷所有的父View,直到ViewRootImpl,這樣就修改所有的父View中的mFocused變量了,之后有按鍵事件時(shí)就按這個(gè)路徑傳遞KeyEvent,這也在上一篇中也有分析。
ViewGroup的requestFocus方法
ViewGroup復(fù)寫了View的requestFocus(int direction, Rect previouslyFocusedRect)方法,如下:
@Override
public boolean requestFocus(int direction, Rect previouslyFocusedRect) {
//獲取ViewGroup相對(duì)于子View的獲得焦點(diǎn)的順序
int descendantFocusability = getDescendantFocusability();
boolean result;
switch (descendantFocusability) {
//攔截焦點(diǎn),直接調(diào)用自己的獲取焦點(diǎn)的邏輯
case FOCUS_BLOCK_DESCENDANTS:
result = super.requestFocus(direction, previouslyFocusedRect);
break;
//在子View之前,調(diào)用自己的獲取焦點(diǎn)的邏輯,如果不能獲得,遍歷子View,讓先子View處理
case FOCUS_BEFORE_DESCENDANTS: {
final boolean took = super.requestFocus(direction, previouslyFocusedRect);
result = took ? took : onRequestFocusInDescendants(direction,
previouslyFocusedRect);
break;
}
//在子view之后,先遍歷子View,讓子View處理,如果它們都不處理,則再自己處理
case FOCUS_AFTER_DESCENDANTS: {
final boolean took = onRequestFocusInDescendants(direction, previouslyFocusedRect);
result = took ? took : super.requestFocus(direction, previouslyFocusedRect);
break;
}
default:
throw new IllegalStateException("descendant focusability must be "
+ "one of FOCUS_BEFORE_DESCENDANTS, FOCUS_AFTER_DESCENDANTS, FOCUS_BLOCK_DESCENDANTS "
+ "but is " + descendantFocusability);
}
if (result && !isLayoutValid() && ((mPrivateFlags & PFLAG_WANTS_FOCUS) == 0)) {
mPrivateFlags |= PFLAG_WANTS_FOCUS;
}
return result;
}
在這個(gè)方法中ViewGroup根據(jù)自己相對(duì)子View獲得焦點(diǎn)的順序來(lái)確認(rèn)調(diào)用方法的順序。從代碼中可以看出如果一個(gè)ViewGroup要獲得焦點(diǎn)它的邏輯和View是一樣的,而且由于ViewGroup默認(rèn)設(shè)置了FOCUS_BEFORE_DESCENDANTS,如果它再設(shè)置focusable為true,它的想獲得焦點(diǎn)的兒子們就不要指望爸爸主動(dòng)給焦點(diǎn)了??,只能通過自己的requestFocus去獲得。
總結(jié)
簡(jiǎn)短總結(jié)一下本篇的內(nèi)容:
- View的焦點(diǎn)模式可以使用focusable屬性定義,也與clickable屬性有關(guān)聯(lián)
- ViewGroup在View的基礎(chǔ)上定義了自己相對(duì)于子View的處理焦點(diǎn)的順序
- View通過requestFocus方法獲得焦點(diǎn)
- ViewGroup復(fù)寫了requestFocus方法,加入了順序判斷
到這里按鍵事件的分發(fā)和獲得焦點(diǎn)的過程分析完畢,但事情還沒完,當(dāng)按下按鍵時(shí)會(huì)發(fā)現(xiàn)焦點(diǎn)會(huì)在View之間移動(dòng),那按鍵事件是怎么轉(zhuǎn)換為焦點(diǎn)View的變化的呢?請(qǐng)看下篇分析: Android TV開發(fā)按鍵與焦點(diǎn)深入分析(三)--按鍵事件轉(zhuǎn)換成焦點(diǎn)移動(dòng)的過程