Merge commit '31bbf9cbff8d5db6ab3b1cd93497045acdb8f74a'
* commit '31bbf9cbff8d5db6ab3b1cd93497045acdb8f74a':
Stop trying to play tricks with the focusability of the search widget's
TextView, as we weren't always doing it right, and it doesn't seem to
help or hurt the frequency of the home screen sliding up when the
widget is selected (that seems to be separate, see http://b/1819752).
onPrepareDialog() is called after a dialog was created/shown at least once. But
onPrepareDialog() does not mean the dialog will be shown. Thus Home would
sometimes lock itself without showing the dialog the user would normally use to
unlock the workspace.
SearchManager.isVisible() is a hidden method that should
not be used by applications. Also, SearchManager.stopSearch()
already checks whether the search dialog is visible before
tryinf to dimiss it, so the check in Launcher was redundant.
Home was incorrectly treating apps launches as subactivties launched to obtain results.
This resulted in a protective flag being set when it should not have been.
Dismisses the popup window upon configuration change and correctly restores the
window after the new activity is created. This change also saves/restores the
current gesture and its match. This change also fixes the handling of the back
key when creating a new gesture-based shortcut: the gestures pad is not dismissed
anymore when pressing back in one of the shortcuts dialogs.
Previously, pressing back in a dialog on top of the gestures panel would
always dismiss the gestures panel. This is because the UP event for the
BACK key is sent to the underlying window after dismissing a dialog.
This fix simply checks for DOWN events only.
The GesturesActivity was crashing when changing the orientation while
renaming a gesture. This was due to unimplemented support for orientation
changes.
Instead of waiting for Xms after a finger up event to start the recognition process,
do it right away on a finger up event. This provides immediate feedback.
A dialog can be dismissed without being cancelled. This change simply
adds a dismiss listener to the Add dialog in Home to make sure the
workspace is properly unlocked when the dialog is dismissed.
Moving the trackball up or down on a screen in Home could send the focus
to the left/right, which can be confusing. This issue was introduced by
a change in the way addFocusables() work and Home did not respect the
new behavior.
Joe Onorato
Mike LeBeau
Dianne Hackborn
Android (Google) Code Review
Romain Guy
Bjorn Bringert
Karl Rosaen