summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorChavi Weingarten <chaviw@google.com>2018-02-23 00:27:54 +0000
committerchaviw <chaviw@google.com>2018-02-22 17:14:39 -0800
commitb736e3215b8e0afeecd053a43fde6c002ca5c2a0 (patch)
tree0a3239558201b2d9cac27bf253e7ed22f0f77ac1 /tools/aapt2/java/JavaClassGenerator_test.cpp
parent3d529f764e4b1ef37db095d1436729e8f7b7c430 (diff)
Use destroy in transaction for animation
Previously, the code calls destroy which will be invoked immediately so there needed to be ways to delay destroy. This caused some overhead where there needed to be Runnables to ensure client state updates were called before the destroy. Instead, use the Transaction.destroy so the destroy doesn't get invoked until apply is called. This allows any other client states to get updated before the destroy is called. This is specifically necessary for reparent calls since a Surface can be reparented from a Surface that's about to get destroyed to a valid Surface that's not getting destroyed. This change ensures that Surfaces will get reparented before Surfaces are destroyed when Transactions are applied. Original CL: ag/3573288 Reason for revert: Original issue is fixed in ag/3647191. Fixes: 72953020 Test: SurfaceAnimatorTest Change-Id: I8bc58e0efc2ae1558c122a40eb52e9c874c0c997
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions