summaryrefslogtreecommitdiffstats
path: root/packages/Shell
diff options
context:
space:
mode:
authorAdam Powell <adamp@google.com>2013-10-15 15:30:06 -0700
committerAdam Powell <adamp@google.com>2013-10-15 18:10:41 -0700
commitbdb5ac7ddbabec0ba947a32937d8b95738d513dc (patch)
treed7f476f381d734668ff02fab20c28006ce141b6c /packages/Shell
parentf847c3b014ab49fae6bbbc9dd7aac199b31467df (diff)
downloadframeworks_base-bdb5ac7ddbabec0ba947a32937d8b95738d513dc.zip
frameworks_base-bdb5ac7ddbabec0ba947a32937d8b95738d513dc.tar.gz
frameworks_base-bdb5ac7ddbabec0ba947a32937d8b95738d513dc.tar.bz2
Fix dodgy states of keyguard transport controls
If a layout has already been requested when we want to show the correct widget pane, post the event for later and immediately return. This works because PagedView has some interesting ideas about maintaining a consistent state. It will attempt to recalculate the current page position during measurement, but thanks to a reliance on this measurement to establish scrolling boundaries that scrollTo uses for clamping plus other code that depends on the idea that it can add a new widget pane view and immediately scroll to it, this attempt to scroll fails if the target page was added and measurement is not yet complete. This patch ensures we don't hit these edge cases in a few known ways. While this ends things in the correct state, it predictably has a few visual artifacts. Situations where things would completely fail before, positioning pages incorrectly or fading out wrong pages now will briefly flash and fade the widget frames or in some cases will visibly animate from the starting page to the correct one. We should address these issues in a future release. Bug 11217368 Bug 9760604 Change-Id: I989d03b5bfdd5b6403a6b67a8aae7585ca0c8ae0
Diffstat (limited to 'packages/Shell')
0 files changed, 0 insertions, 0 deletions