| 67f948f353b652d3373c7bdb0c2a8715e8b4e9f6 |
|
10-Jul-2017 |
Diego Perez <diegoperez@google.com> |
Fixes animated vector drawable test
The frame cleanup in the Choreographer was not cleaning the
AnimationHandler.
Test: Fixes existing test
Change-Id: I3f80d3518c7aab1ffebd6f3f2045874be3d32daf
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 878037d8f533ca51121d0dc035181e5ecb2762cf |
|
07-Jul-2017 |
Diego Perez <diegoperez@google.com> |
Clean-up any choreographer callbacks after render
After calling render, any animation callbacks need to be removed so they
are not executed in the next frame.
Test: Existing tests pass
Bug: 63380076
Change-Id: If3974d84b47a48ee7c769f31c6c179ccc6e8f7c2
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| d73404483cb16edaa81259fbc7a19627f2555bc2 |
|
30-Jan-2017 |
Diego Perez <diegoperez@google.com> |
Fixes for animated vector drawables
- Make sure that all ImageViews containing animated vector drawables
have the animation started.
- VGroup does not need to copy the children as they are copied by the
VectorDrawable initialization
Test: Covered by existing animated vector drawable tests
Change-Id: Ic0fc09ee5c98b3747dbc6fe311cdeea2c8dba380
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 3c7963bb563cef3ed2924461b3b8cb9c4650f9b2 |
|
06-Apr-2016 |
Deepanshu Gupta <deepanshu@google.com> |
Add missing setAccessible to Choreographer's threadInstance
Change-Id: I753660cf68ba5a9c375942222e32059d952739bb
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 405d10472d7b8ba7ff86f46e734195128709a829 |
|
06-Apr-2016 |
Deepanshu Gupta <deepanshu@google.com> |
Clear ThreadLocal storage from Choreographer
Change-Id: I5abb5c68a635e7808b0a036ba4d9971cd0139aa3
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 344cbc9b8ed3ae06a5b183d684df0399fef59879 |
|
02-Dec-2015 |
Deepanshu Gupta <deepanshu@google.com> |
Revert "Revert "Add support for Choreographer animations""
This reverts commit 8390b2ac85765e768d4b685077a96e6395d208b4.
The build break should now be fixed by
cbb1ba7f493116882b79578ec68646366f29cde4
Change-Id: I9bf21cc6dbdb5d515a665384dc6dfa464c3e6e2e
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 31bedba360a3bba732b63566ddb0521f1765753e |
|
02-Dec-2015 |
Diego Perez <diegoperez@google.com> |
Revert "Add support for Choreographer animations"
This reverts commit 29ed07524ce0fc2e5950f5340d306247145d0efa.
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| 67edd77d7aae7770b691b45e00c67d7f42e0316d |
|
14-Oct-2015 |
Diego Perez <diegoperez@google.com> |
Add support for Choreographer animations
First step to add support for Choreographer based animations. The
Choreographer_Delegate avoid using a handler so the animation callbacks
can be called on-demand (by using doFrame). This allows things like
frame by frame animation or selecting a specific frame, and doesn't need
a separate thread to run.
The CL also changes the System and SystemClock implementations to allow
to set specific times. Because animations heavily rely on the system
time, this allows controlling it. It can also be useful to ensure that
the rendering produces a deterministic result when using controls like
the Calendar widget.
Change-Id: Iff221d2698a82075cafbb60f341be01741f7aa13
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|
| ab775ecdd189b32e35b0d3f4a821502f88b03a4b |
|
24-Jan-2014 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Move frameworks/base/tools/ to frameworks/tools/"
This reverts commit 9f6a119c8aa276432ece4fe2118bd8a3c9b1067e.
/frameworks/layoutlib/bridge/src/android/view/Choreographer_Delegate.java
|