* commit 'd21f9404da5c8cdc959b483a40876b02ced35e43':
Disabling auto restore of widgets. > Always show "Setup" button for a widget which has a config activity.
> Instead of resizing the rect for dragoutline in onDrow, store the resized rect itself
> Remove unnecessary inverse matrix calculation
Change-Id: If13c3c5aaecba5a1d3a4f5d39199ed82e9662c62
* commit 'd468ee90911bee4d83e119500b52df1984107411':
Reloading launcher whenever there is an external update to contentprovider, irrespective of the uri
If you click at the icon with mouse, then release without moving,
the framework won't generate DRAG_LOCATION events, and we'll assume
the the drag ended at (0,0) coordinate.
Fixing by updating coords at any event that has coordinates.
Bug: 22028725
Change-Id: I1872b479035e14aa9fece1532b05194fa86a4907
This fixes perhaps an old bug.
If we started an accessible drag for an only item on a page,
then uninstalled the app while dragging, the page was removed
without unsetting its accessibility delegate. Later, the system asks
the delegate to do something, but the drag is over, and some pointers
are null, so everything crashes.
Fixing this.
Bug: 22028725
Change-Id: I85adcd42ae896603634994e20a7790792f7e84b1
(cherry picked from commit de1e67c388)
We don't want to start a framework DND (with drop shadow etc.) in the accessibility mode.
Besides, framework DND fails to start and immediately cancels the DND operation
if it's started in the accessibility mode. Presumably, this happens because
the finger doesn't press the screen when this happens.
The right solution is not to instantiate a drag driver at all when an accessible
DND starts, which is what this CL does.
Bug: 22028725
Change-Id: Ic743ba3f8de037c15d4e70e3b7687cdd3518b2a3
This fixes perhaps an old bug.
If we started an accessible drag for an only item on a page,
then uninstalled the app while dragging, the page was removed
without unsetting its accessibility delegate. Later, the system asks
the delegate to do something, but the drag is over, and some pointers
are null, so everything crashes.
Fixing this.
Bug: 22028725
Change-Id: I85adcd42ae896603634994e20a7790792f7e84b1
When drag exits Launcher window (for example, goes to Shelf) launcher doesn't get notified
and thinks the drag is still over it. For example if there is a moved shaking icon in Hotseat,
it will keep shaking.
Fixing this.
Bug: 22028725
Change-Id: Ie57572a57a324d426c9f6e57dc0bba56630e92df
There was a jump upon a transition from DragView to the framework shadow
for hotseat icons (which are scaled down).
Bug: 22028725
Change-Id: If4f5ed4501836667ff3a8eaa9da4577bdf98e880
Upon the end if the growth animation for DragView, we hide DragView and
show the framework DND drag shadow. Rounding problems caused shifting of the
drag image by 1 pixel when the transition happened.
Bug: 22028725
Change-Id: I2a2275a6d18c1a10ceecaecf8a279c6d11d8c7d8
- There was an issue with the previous logic where the test of whether
the search bounds changed would always be false if valid search bounds
were given. This in conjunction with the fact that the padding was
changed to only take the bounds left/right into account, meant that
the container bounds would not be updated if the search bar bounds
shifted via the insets.
Bug: 22918919
Change-Id: Ia810ddc7a56eae4afc0c7cd558fa6dc9e8e7a95b
When the longpress clings such like welcome message appears,
the key events should be limited as follows:
- normal keys (generates printable glyphs) should be prevented,
otherwise they come to the underlying searchbox.
- it should be dismissed on Menu keys, which goes to the overview
mode.
Bug: 22982955
Change-Id: I7272b0809bfaa3c08ba77b01383cf54f19390d95
Sunny Goyal
Winson
Vadim Tryshev
Adam Cohen
Jun Mukai