25160db73f37619a26a3d87a06625925d881b0fd |
|
19-Apr-2016 |
Jorim Jaggi <jjaggi@google.com> |
Optimize some binder calls when recents configuration changes Bug: 28122871 Change-Id: I54249428792c3ad4b3b6d3dcc0f405675b3b23b4
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|
67c79578f94646bade5d336af0d4491179c1b37d |
|
13-Apr-2016 |
Winson <winsonc@google.com> |
Fixing various layout issues when docking - Fixing regression where we were scrolling to front immediately on dragging-to-dock a task, we should only scroll to the front on configuration change. - Accounting for the inset when calculating the final stack bounds (similar to b/27921362) - Fixing issue with task views being clipped as user drags a view due to the bounds of the view changing. We manually now set the frame on the view to the current stack task bounds. - Simplifying calls to animate the task view bounds - Removing old instance state code Change-Id: I17d3e33e159ff250c11a504ef87558051926a974
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|
500ba75c9a53786ce3f60a9cd985b6cc29eb665d |
|
30-Mar-2016 |
Winson <winsonc@google.com> |
Disabling the nav bar scrim when Recents is docked. Bug: 27869246 Change-Id: I554b299c7e577f40811fc02d6ff4a46313ff1622
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|
44849b8abdcdefbe3112324d98afdea220a37376 |
|
29-Mar-2016 |
Winson <winsonc@google.com> |
Should not update initial state at all on resize. This fixes an issue with the stack scrolling upon resizing. We only need to update the initial state if docking, or upon rotation. Change-Id: Ie59ed72cb22c9b000289db3f04b1a71ad5f64816
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|
619e40cd56266a362ab7da80cb9e4eba6c33b204 |
|
26-Mar-2016 |
Winson <winsonc@google.com> |
Fix config change layout. (Part 2) - Fixing issue where the initial state was not correct after rotating the screen. We needed to update the layout, but that could only be done after the task stack view is laid out. Now we set a flag to update the initial state of the layout on configuration change, and only scrolling to the front when it makes sense. Change-Id: I2586b90d1e869708b97bcd1a4446f4d87fa521cc
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|
e693aafe0511c2a7ffc571b22abeefba44046225 |
|
01-Mar-2016 |
Winson <winsonc@google.com> |
Disabling timer - Disabling the timer by default - Adding flag to enable/disable paging (disabled by default). When disabled, the second tap will just launch the next task. - Updating the initial state to put tasks at specific points on the curve. This allows us to allocate specific space for the front most tasks, as well as the tasks behind it. - Removing hardware layer config (no devices targeting N depend on it) - Fixing issue with the header not having the final dim applied when transitioning into recents. - Fixing issue where the stack range would not be reloaded after docking or undocking a task. Bug: 27409035 Change-Id: I13a03fba2b1a770f15d0033d43ef4c28415041c9
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/events/activity/ConfigurationChangedEvent.java
|