| commit | f7917e656b94ec2adfc3fa826e093665d39748d2 | [log] [tgz] |
|---|---|---|
| author | Chet Haase <chet@google.com> | Mon Dec 19 15:49:42 2011 -0800 |
| committer | Chet Haase <chet@google.com> | Mon Dec 19 15:49:42 2011 -0800 |
| tree | 810e97e5f32b2fd7af5d9d1b2ce9b51e2e691ab9 | |
| parent | 01583ef715641c8a3ce68269b091e75adbe9335a [diff] |
Fix AnimationDrawable double-start bug AnimationDrawable.setVisible(true, true) was not correctly recording the fact that it had started the animation, so it was possible to call start(0 immediately afterwards and have two animations running on the drawable in parallel, resulting in incorrect frame ordering. Issue #5782773 Change-Id: Ifc328f755a51d10ab76b84006d1999df03d2dca1