diff options
| author | chaviw <chaviw@google.com> | 2018-04-16 15:29:38 -0700 |
|---|---|---|
| committer | chaviw <chaviw@google.com> | 2018-04-17 10:06:48 -0700 |
| commit | e390cbd937fb7edbcba8abf8314f9c8074838684 (patch) | |
| tree | 769478d0ad16c34b8c8f88243d38c6e19591c254 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 167032ab002714d26a14735bbcdc072c5fa693b7 (diff) | |
Don't start Window enter animation as a result of AWT becoming visible.
There are some cases where AWT becomes visible without an animation. It
will then start a WindowState enter animation if WS is not visible yet.
However, this is problematic since the WS may not be ready to become
visible yet. For example, relayout may not have been called yet to
create a surface and the size of the surface is not yet set. This causes
problems when determining the position of the leash when the animation
is created. Instead allow the WS relayout to handle starting the
enter animation so the WS is set properly.
As for the case where AWT is becoming not visible without an animation, but
WS is still visible, create an exit animation for the WS. This is
because there won't be a client to trigger this animation.
Change-Id: Ic9215a0c96f219f5bc87b16067755af582883a5d
Fixes: 77447982
Test: Issue from bug
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions