summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorRiddle Hsu <riddlehsu@google.com>2019-02-22 12:44:12 +0800
committerRiddle Hsu <riddlehsu@google.com>2019-02-26 14:39:08 +0800
commitb8d704b96aee2479ffbee1d340dfe18657ee86cf (patch)
tree9d7f2f06e1bc9a41ef63d97ef9ed1a0699a5fa23 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parentddc0fa515588f6545f7ffbc4e9d03b55565020f8 (diff)
Don't destroy surface if there is no active animation to cancel
It is possible that mAnimatingExit is true but there is no animation associated to the window because its parent is waiting for transition. (WMS.tryStartExitingAnimation, WA.applyAnimationLocked, WS.isAnimating) It may cause flicker during relayout to visible because the surface is destroyed directly. This change restores the condition as commit cef37fb4 (removed in commit a5e10572) to avoid the case. Bug: 113867701 Test: manual - While device is locked with a top show-when-lock activity, launch another show-when-lock translucent activity in the same task (for transition type activity_translucent_open_enter that is easy to hit the timing) and observe there is no flicker (black screen). Change-Id: I6d47255660d26d9c67bd1a9076a2f14e7ce75cfd
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions