summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
diff options
context:
space:
mode:
authorAndrii Kulian <akulian@google.com>2019-01-08 15:03:50 -0800
committerAndrii Kulian <akulian@google.com>2019-01-25 12:32:35 -0800
commitd70cdb93b84830922b8707e03bb1f28b85d2debd (patch)
tree71a63a770b580ec1dc28235fca010ea7bace9853 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
parent996df0dbca73e09f9fbb793c0f90dc3d0b4892da (diff)
Report top resumed activity state change
Some system resources can only be accessed exclusively by a single client at a time. Previously there was only one resumed activity in the system at any point, so apps were usually trying to obtain such access in onResume. With multi-resume this is no longer a good place to do so, because: - onResume may be called for activity that is not on top; - top resumed status may be switched between different resumed activities in multi-window mode by tapping on them. This adds a separate callback to inform apps about top resumed state gain and loss events. The following rules apply: - both callbacks can only be delivered between onResume and onPause; - top resumed state loss always follows top resumed state gain; - the callbacks are optional, activity can go from onResume to onPause without obtaining top position. Bug: 117135575 Test: atest CtsActivityManagerDeviceTestCases:ActivityLifecyclePositionTests Change-Id: I45797afe47b166b22cfb75b64132b22d3fb4ecc7
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions