alexjlockwood / ShapeShifter

SVG icon animation tool for Android, iOS, and the web
https://shapeshifter.design
Apache License 2.0
3.97k stars 200 forks source link

Delayed Animations Are BAD #306

Open mikecprogram opened 6 years ago

mikecprogram commented 6 years ago

So I was trying to build a cup with water in the shapeshifter, and after I exported the AVD into Android Studio, the animation fill was totally wrong - both files, my export and my final fix are attached, so I added nothing animation(just another one but without nothing - goes from 0 to 0) and it didn't fix it either.. So I added the following to each vector who had delayed animation <objectAnimator android:propertyName="trimPathStart" android:startOffset="0" android:duration="0" android:valueFrom="0.5" android:valueTo="0.5" android:valueType="floatType" android:interpolator="@android:interpolator/fast_out_slow_in"/> And it fixed it. Can you please fix this in the ShapeShifter site? It is very helpful tool and I really like using it! :)

drawable.zip

alexjlockwood commented 6 years ago

Thanks for reporting!

Could you post the contents of the .shapeshifter file for your project so I can look into it?

You can go to "File --> Save" to download the .shapeshifter file. Then just open it up in a text editor, copy its contents, and post it to this bug report.

mikecprogram commented 6 years ago

As of right now, I'm not near my computer. I'll do it first when I'll be around it... But the ShapeShifter isn't the problem! It's the Android AAPT.. just if I add those lines with the parameter that will be animated with delay (AKA: startOffset) with the startOffset=0 and duration=0, its fixing it..

alexjlockwood commented 6 years ago

Ahh OK... well, in that case the .shapeshifter file would still be useful. There may be a way I can modify shape shifter to temporarily workaround the issue, even if it technically is an issue with Android AAPT. :)

alexjlockwood commented 6 years ago

Uploading a sample project demonstrating the issue would also be helpful if you have one... it sounds like this is something I could report directly to Google. I've sent them many bug reports like this... haha