BTW, I think I found a bug in the NoA library when using float values.
If I set up an animation using the scale properties, and feed them float values, it seems to treat them like int values that are rounded down.
For example, in this animation:
Dim animX As noaObjectAnimator
animX.InitializeFloat(someView, animX.PROPERTY_SCALE_X, 1, endScale, "")
...I want the view to "bulge" a bit, so I set endScale to 1.3 (that is, 1.3 times bigger than the original size). However, it treats it as 1.0 (no change in size) no matter what value I use between 1.1 and 1.9. If I set it to an int like 2, it animates properly.
Similarly if I try to shrink the view down to half size (0.5), it shrinks it down to nothing (as if it was rounding down to the next smallest int - zero).
In the docs, the method is also documented with int arguments instead of the floats I expected:
InitializeFloat (target As Object, propertyName As String, StartValue As Int, EndValue As Int, EventPrefix As String) As ObjectAnimator
Scale takes float values in the AnimationPlus library. Should it also do that here, or are they using a different scheme?
Thanks!