glomadrian/loading-balls

A highly configurable library to do loading progress with animated balls

loading-balls's Issues

java.lang.VerifyError on 6.0

Just got a Crashlytics report for this library used in a production app for java.lang.VerifyError

Please fix

Crashes in Android 5.0.x

Crashes in Android 5.0.x, but it is normal in other system version. No stacktrace.

Set Cancelable Flage

Hi the loader is awesome.
Just wanted to add not an issue actually but a suggestion.
Can we have setCancelable("false") something like Dialog.

Thanks,
Abhijit

Wrong gradle depencency in README

You have a wrong gradle depencency in your readme:

  compile 'com.github.glomadrian:loading-balls:1.1@aar'

It should be (according to your maven repository):

compile 'com.github.glomadrian:loadingballs:1.1@aar'

-> without the dash between "loading" and "balls".

ClassNotFoundError : BaseInterpolator

Hi,,

On some devices (eg : my Asus Zenfone 2), using BallView make my app crash (i receive a SIGSERV error).
After some researches, i found that the error was due to the usage of BaseInterpolator class that cannot be found.
Indeed, this class is only available from API 22, making the app crash.
http://developer.android.com/reference/android/view/animation/BaseInterpolator.html

One solution is to replace the BaseInterpolator reference with Interpolator interface.

Add support for creating BallView programmtically

It would be nice if you add support for creating the BallView programmtically. You should add getters and setters for all the custom attributes (numberOfBalls, ballSize, minBallSize, maxBallSize, .....).
Otherwise I have to implement AttributSet just available as an interface.

Auto start/stop with visibility change

Could you please add an option to auto start and stop the animations when the visibility changes i.e. start animations when View.VISIBLE otherwise stop animations (both INVISIBLE and GONE)?

I am trying to to manually start, stop and restart animations but I am getting a lot of NullPointerExceptions because of null ballPathAnimator. The animator is created in the onSizeChanged(...) and that method is not yet called when a Fragment's onResume() is called, thus NPE crash. Automatic start/stop will solve all this troubles. Thank you for this beautiful loading indicator.

Balls don't always respect configurations

I have included the balls in the xml of several fragments complete with customization but it only a few of them respect the customization. The other instances default to the configuration that comes with the library, i.e 3 balls of yellow, blue and red color.

This is my implementation:
<com.github.glomadrian.loadingballs.BallView android:id="@+id/ballView" android:layout_width="100dp" android:layout_height="100dp" android:layout_centerInParent="true" android:layout_gravity="center" android:layout_margin="30dp" lib:ball_colors="@array/color" lib:balls="5" lib:enable_size_animation="true" lib:max_ball_size="12dp" lib:min_ball_size="5dp" lib:movement_cycle_time="1500" lib:size_cycle_time="500" />

where the array of color has 5 different shades of red.

High CPU use after stopping the animation with size animation enabled

Calling stop() does not disable the animation fully and takes a lot of CPU. The stop method incorrectly calls start() instead of stop on the ballSizeAnimator:

  public void stop() {
    ballPathAnimator.stop();
    if (sizeAnimationEnabled) {
      ballSizeAnimator.start();
    }
  }

android:allowBackup=true shouldn't be used in the library

Using the above in the line is causing manifest merger failed.