This is an interesting problem. When the ActionMode is active the back key event is consumed internally. The event is not propagated to either onBackPressed()
or onKeyUp(int keyCode, KeyEvent event)
callbacks.
Fortunately, you can use dispatchKeyEvent(KeyEvent event)
which is still called.
@Override
public boolean dispatchKeyEvent(KeyEvent event) {
if(mActionModeIsActive) {
if (event.getKeyCode() == KeyEvent.KEYCODE_BACK && event.getAction() == KeyEvent.ACTION_UP) {
// handle your back button code here
return true; // consumes the back key event - ActionMode is not finished
}
}
return super.dispatchKeyEvent(event);
}
You might wonder what will be the behavior in case you have a submenu in the ActionMode and you close it with the back key. In this case dispatchKeyEvent()
is not called so you can safely use the code.
The above code works also with ActionBarSherlock. The only problem I found is on Android 3.1 device when the native ActionMode is used, in this case the dispatchKeyEvent()
is not called. Use ActionBarSherlock's ActionMode to solve it.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…