summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorFilip Gruszczynski <gruszczy@google.com>2015-12-04 15:45:35 -0800
committerFilip Gruszczynski <gruszczy@google.com>2015-12-04 17:30:52 -0800
commitdba623ae5648923e06157d53fcc0ab8a09a79870 (patch)
tree5533c0d2ff1f5e7a99bfd44c8ba2912ec9f4f524 /tools/aapt2/java/JavaClassGenerator.cpp
parente920098f31860824ca714f10b2e72dbff5442184 (diff)
Don't lose stopping state when getting paused confirmation.
In some cases we request pause and soon after request stop of an activity. An example of this is maximizing an activity in side by side mode when recents are visible. First, we add recents to a list of activities to be stopped (because it becomes invisible), then we request a pause (because we resume full screen activity and pause all other stacks) and finally request a stop (from the list to which we added the request). The activity now will be put into pausing state (requesting pause), then stopping (requesting stop), then paused (confirmation comes from the activity) and stopped (another confirmation comes from activity). If we switch from stopping to paused, the stop confirmation will become confused. Bug: 25729693 Change-Id: I935acd71a28f3d0882f608bdd4d7216cd08ba2eb
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions