I am trying to animate two layers of a drawable to achieve the effect of the post-Honeycomb indeterminate progress indicator. The XML is very straightforward but it would seem t
There is indeed a platform limitation, although it's not what you might think. The issue is that pre-API11, RotateDrawable
had some crude code in it to require that the animation rotate clockwise by checking if toDegrees
was greater than fromDegrees
; if not, the two were forced equal to each other. If you modified your example to have the second item move in a forward direction (from 0 to 720, or even -720 to 0), both images would animate fine on all platforms; though I realize that defeats the purpose of what you're aiming for.
Take a look at the cached version Google Codesearch has of RotateDrawable.inflate()
, which is the 2.3 version of the method used to turn the XML into the object, and you'll see what I mean.
RotateDrawable.java ...the offending code is around line 235...
float fromDegrees = a.getFloat(
com.android.internal.R.styleable.RotateDrawable_fromDegrees, 0.0f);
float toDegrees = a.getFloat(
com.android.internal.R.styleable.RotateDrawable_toDegrees, 360.0f);
toDegrees = Math.max(fromDegrees, toDegrees); //<--There's the culprit
This takes an XML block like the second item that you have there, and turns it into a RotateDrawable
that ends up with the same value for fromDegrees
and toDegrees
(in your case, 720), causing the image to simply stand still. You can visible test this by setting the start value to some value not a multiple of 360 (like 765). You'll see that the image still does not animate, but is rotated to the initial coordinate.
This awkward check was removed in the Honeycomb/ICS sources, which is why you can do backwards rotation on those platforms. Also, it doesn't look like there is a way to set these values from Java code, so a custom RotateDrawableCompat
may be in your future :)
HTH