Merge commit '91a9c9636f10f1e12cd1f660b2e330634fbdc7dc'
* commit '91a9c9636f10f1e12cd1f660b2e330634fbdc7dc':
When initiating a drag and drop from a folder in home, you could sometimes see
Merge commit 'fca59c759ef9c7cc2fc062d14ede8bd57254abbf'
* commit 'fca59c759ef9c7cc2fc062d14ede8bd57254abbf':
Fixes#1824492. Removes the clock from the default Home layout.
Merge commit '3003fb8214e512ee7b8eb62b10b7446177e0682c'
* commit '3003fb8214e512ee7b8eb62b10b7446177e0682c':
Tweak thread priorities in Home to make first boot experience a little better.
Merge commit '6fefcf1f83ba05e898ea7164a68dcced657bb43e'
* commit '6fefcf1f83ba05e898ea7164a68dcced657bb43e':
Change recognition matchin in Home to immediate mode.
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.
Merge commit 'ae4f575911d0c17de8d687a8fa092b0aa8360243'
* commit 'ae4f575911d0c17de8d687a8fa092b0aa8360243':
Improve the threading model in the gestures settings activity.
Merge commit 'aad5ef44c665fc4ce143a61c009dc04be3ab0437'
* commit 'aad5ef44c665fc4ce143a61c009dc04be3ab0437':
Fix issues with how the gestures pad was hidden when leaving Home.
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.
Remove shortcuts from folders (closed and opened) whenever the user
uninstalls an application. Home was removing shortcuts from the
workspace and the database but was not updating the UI correctly
when running.
Dragging an icon out of a folder was showing a gray background. This was due to the icon's drawing cache background color. This fix simply temporarily resets that color when capturing the view into a Bitmap.
Merge commit '8283ccff7c44e3f2a62496167159228eb50706b6'
* commit '8283ccff7c44e3f2a62496167159228eb50706b6':
Do not force the soft keyboard open if the search widget is already at the top of the screen.
Forcing the soft keyboard open is done at a specific time when animating the
search widget to the top of the screen in order to time the two animations well,
but we were doing it anyway even if the search widget was already at the top of
the screen and didn't need to animate.
Okay, so git does kinda rock when you're on a plane. :)
Merge commit 'c2ad7a6e1571f933f4bc8ceaee5c745a96aaaf68'
* commit 'c2ad7a6e1571f933f4bc8ceaee5c745a96aaaf68':
Fix for #1855127. When Home cannot decode an icon, it should not interrupt the loading of the workspace, but fallback to the default package icon.
Merge commit '583ed3ba08644912ec0f3ec8ceb939f9eb0b8e86'
* commit '583ed3ba08644912ec0f3ec8ceb939f9eb0b8e86':
* re-scale icons that are loaded using different denstiy metrics.
Merge commit '4c58c485d8c02f8ca7e8b4d93140440f6a3a5131'
* commit '4c58c485d8c02f8ca7e8b4d93140440f6a3a5131':
Fixes#1844053. Home was accepting all drops, even when there was no room left for a drop. This change fixes this while retaining the 'snap to vacant cell' ability added in Cupcake.
When dragging between workspaces in rapid succession, the canceling of the
original long-press timer wasn't being triggered correctly. (When the timer
fires, it might read an invalid Workspace.allowLongPress() value.)
This patchset correctly cancels any pending long-press timers once a desktop
scroll begins, and we don't need to rely on the allowLongPress() value.
Merge commit 'ecadabf578369def58e343c1adbb5537aa9801e4'
* commit 'ecadabf578369def58e343c1adbb5537aa9801e4':
Fixes#1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.
* changes:
Fixes#1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.
Merge commit 'c7a21b5fe07837a1146f9781c1787100b8c04e84'
* commit 'c7a21b5fe07837a1146f9781c1787100b8c04e84':
Modify comments in Launcher strings for global search.
Romain Guy