Below attached is the code snippet

    private DotsTextView mLoadingDots;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_splash);
    mLoadingDots = (DotsTextView) findViewById(R.id.dots_text);     
    mLoadingDots.start();
            mLoadingDots.showAndPlay();

in my layout ive added

       <pl.tajchert.sample.DotsTextView
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:id="@+id/dots_text"
        android:textSize="50sp"
        android:paddingBottom="10dp"
        android:layout_marginLeft="5dp"
        dots:autoplay="true"
        dots:period="250" />

in my build.grade dependencies { compile 'pl.tajchert:waitingdots:0.2.0' }

changing to 0.1.0 gets it working but the animation is weird it comes from left to right then starts jumping(lagging all the way)

tested on nexus 5 and moto g1 running 5.1

I'm using version 0.2.0 of your library and the dots do not animate. isHide() returns false and isPlaying() returns true. The code I'm using is at https://github.com/thevoiceless/TvBluetoothSetup/tree/waitingDots

It may be worth noting that I am running AOSP compiled for the device, not the stock software from Google (although they should be the same aside from proprietary Google stuff).

Let me know if you need more information.

Hi. This is what happens when I try to use it on my splash screen

[http://imgur.com/PiDE9GJ](image url)

Here is my layout.

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:dots="http://schemas.android.com/apk/res-auto"
    android:orientation="vertical"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <RelativeLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <ImageView
            android:src="@drawable/kr_logo"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_centerVertical="true"
            android:layout_centerHorizontal="true"
            android:id="@+id/imageView" />

        <pl.tajchert.sample.DotsTextView
            android:text="Klickrent"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:id="@+id/dots"
            android:textSize="56sp"
            android:textColor="@color/black_overlay"
            dots:autoplay="true"
            dots:period="1000"
            android:layout_below="@+id/imageView"
            android:layout_centerHorizontal="true" />

    </RelativeLayout>

</LinearLayout>

And styles are:

<style name="FullscreenTheme" parent="Theme.AppCompat.Light">
        <item name="android:actionBarStyle">@style/FullscreenActionBarStyle</item>
        <item name="android:windowActionBarOverlay">true</item>
        <item name="android:windowBackground">@null</item>
        <item name="metaButtonBarStyle">?android:attr/buttonBarStyle</item>
        <item name="metaButtonBarButtonStyle">?android:attr/buttonBarButtonStyle</item>
</style>

Issue: https://github.com/tajchert/WaitingDots/issues/10

Using you library in our project (thanks a lot for it) in which we use CanaryLeak I've found two leaks in your code:

1. There are some anonymous AnimatorUpdateListener defined that holds a reference to the context.
2. There are some anonymous TypeEvaluator implementations that because they holds references to their parent class and this one to the context leak memory too.

Fixes #7

If the SpannableString consists solely of spans, the spans aren't being drawn, or something like that. Adding an Zero Width Space (\u200B) works around this.

References:

• http://stackoverflow.com/questions/26399111/android-edittext-how-to-create-an-empty-bullet-paragraph-by-bulletspan
• http://stackoverflow.com/questions/20069537/replacementspans-draw-method-isnt-called

Currently I get a manifest merging error because my app sets android:allowBackup="false" and this conflicts.

Library projects shouldn't be setting this.

Using you library in our project (thanks a lot for it) in which we use CanaryLeak I've found two leaks in your code:

1. There are some anonymous AnimatorUpdateListener defined that holds a reference to the context.
2. There are some anonymous TypeEvaluator implementations that because they holds references to their parent class and this one to the context leak memory too.

Hello,

I found a few leaks in the library and I fixed them in this PR. The other functionalities stay put, I didn't actually change anything else.

Best regards