Thank you for the great library! We had the requirement to invert the way the progress is drawing in radial mode, so here is a corresponding pull request of a working version. Hopefully you can include this upstream. Feel free to comment on this request.

More pull requests may follow...

When I call animateProgressFill(n) and then call animateProgressFill(n+10) (where n = {0> n > max-10}) before the the first animation completes, this is thrown:

//The numbers are made up java.lang.IllegalArgumentException: Animation progress (16) is lower than the current progress (17) at com.filippudak.ProgressPieView.ProgressPieView$AnimationRunnable.run(ProgressPieView.java:555) at android.os.Handler.handleCallback(Handler.java:733) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5017) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) at dalvik.system.NativeStart.main(Native Method)

animateProgressFill() and animateProgressFill(int) should check for running runnables and stop them first, then start the current animation

Also, is there any reasons why animating decrements are are not allowed?

Hi, Nice Plugin...I saw your sample app...I want to implement the same in my project but it is in eclipse..it gives error...in init method...can you provide Eclipse version of it library...thanks

Thanks for a great progress pie!!! It's really awesome!

But why the progress is an int and not a double ?! It's really help if it will be a double...

Thanks again!

I'm not exactly sure if this is a library problem or an Android Studio problem because custom views that work with eclipse preview would break in Android Studio for no reasons....

But anyway, here's the stack trace from Android Studio 0.8.4:

java.lang.ClassNotFoundException: com.filippudak.ProgressPieView.R$styleable
at com.intellij.util.lang.UrlClassLoader.findClass(UrlClassLoader.java:148)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at com.filippudak.ProgressPieView.ProgressPieView.init(ProgressPieView.java:95)
at com.filippudak.ProgressPieView.ProgressPieView.<init>(ProgressPieView.java:86)
at com.filippudak.ProgressPieView.ProgressPieView.<init>(ProgressPieView.java:81)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.jetbrains.android.uipreview.ViewLoader.createNewInstance(ViewLoader.java:375)
at org.jetbrains.android.uipreview.ViewLoader.loadView(ViewLoader.java:100)
at com.android.tools.idea.rendering.LayoutlibCallback.loadView(LayoutlibCallback.java:172)
at android.view.BridgeInflater.loadCustomView(BridgeInflater.java:207)
at android.view.BridgeInflater.createViewFromTag(BridgeInflater.java:132)
at android.view.LayoutInflater.rInflate_Original(LayoutInflater.java:802)
at android.view.LayoutInflater_Delegate.rInflate(LayoutInflater_Delegate.java:64)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:778)
at android.view.LayoutInflater.rInflate_Original(LayoutInflater.java:805)
at android.view.LayoutInflater_Delegate.rInflate(LayoutInflater_Delegate.java:64)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:778)
at android.view.LayoutInflater.inflate(LayoutInflater.java:500)
at android.view.LayoutInflater.inflate(LayoutInflater.java:381)
at com.android.layoutlib.bridge.impl.RenderSessionImpl.inflate(RenderSessionImpl.java:400)
at com.android.layoutlib.bridge.Bridge.createSession(Bridge.java:329)
at com.android.ide.common.rendering.LayoutLibrary.createSession(LayoutLibrary.java:332)
at com.android.tools.idea.rendering.RenderService$3.compute(RenderService.java:575)
at com.android.tools.idea.rendering.RenderService$3.compute(RenderService.java:564)
at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:932)
at com.android.tools.idea.rendering.RenderService.createRenderSession(RenderService.java:564)
at com.android.tools.idea.rendering.RenderService.render(RenderService.java:691)
at org.jetbrains.android.uipreview.AndroidLayoutPreviewToolWindowManager.doRender(AndroidLayoutPreviewToolWindowManager.java:604)
at org.jetbrains.android.uipreview.AndroidLayoutPreviewToolWindowManager.access$1900(AndroidLayoutPreviewToolWindowManager.java:80)
at org.jetbrains.android.uipreview.AndroidLayoutPreviewToolWindowManager$7$1.run(AndroidLayoutPreviewToolWindowManager.java:546)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:178)
at com.intellij.openapi.progress.ProgressManager.executeProcessUnderProgress(ProgressManager.java:209)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:212)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:171)
at org.jetbrains.android.uipreview.AndroidLayoutPreviewToolWindowManager$7.run(AndroidLayoutPreviewToolWindowManager.java:541)
at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:320)
at com.intellij.util.ui.update.MergingUpdateQueue.execute(MergingUpdateQueue.java:310)
at com.intellij.util.ui.update.MergingUpdateQueue$2.run(MergingUpdateQueue.java:254)
at com.intellij.util.ui.update.MergingUpdateQueue.flush(MergingUpdateQueue.java:269)
at com.intellij.util.ui.update.MergingUpdateQueue.flush(MergingUpdateQueue.java:227)
at com.intellij.util.ui.update.MergingUpdateQueue.run(MergingUpdateQueue.java:217)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:238)
at com.intellij.util.Alarm$Request$1.run(Alarm.java:327)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

You may close this if it's an Android Studio issue...(or suppress it with View.isInEditMode()...)

And this is how I used it:

    <com.filippudak.ProgressPieView.ProgressPieView
        android:id="@+id/progress"
        android:layout_width="36dp"
        android:layout_height="36dp"
        android:layout_gravity="center"
        android:layout_margin="8dp"
        android:textColor="@android:color/white"
        android:textSize="12sp"
        ppv:backgroundColor="#333333"
        ppv:progressColor="#33DDDDDD"
        ppv:progressFillType="radial"
        ppv:showStroke="true"
        ppv:strokeColor="#33DDDDDD"
        ppv:strokeWidth="1dp" />

Hello mate! Nice work there! Just have to point something out in your example! I think you need to set up a boolean flag and check if the progressCompleted method has been reached and then if the progressChanged is called again remove the drawable that you set and enable the text!

This problem does not exist when using appcompat-v7:20 but with appcompat-v7:21 build fails. Solution, rename attrs "showText" to something diff

Currently, space for a stroke is reserved even if no stroke is to be drawn. You have to manually set strokeWidth to 0 to prevent this. This pull requests is taking into account the showStroke property correctly. It will only reserve space for the stroke if a stroke is requested to be drawn.

This animation is used to fill the remaining of the unfilled pieview. There are 3 defined animation speeds included and the default is set to FAST_ANIMATION_SPEED.

I ran into a crash that was a stupid error on my part, but perhaps could be handled more gracefully by the library or at least be well-documented. If I set a progress value that is outside the range of 0 to max, I get a crash.

I could see perhaps a modification to this library that, when receiving a progress value, floors or ceilings it to the acceptable range. For example, if a progress of 6 is set on a pie view with a max of 4, the effective progress value would become 4. Likewise for negative numbers, if progress is set as -3, then the effective progress for display becomes 0.

If you'd rather not sanitize inputs in that way, I'd suggest either a note about it in the documentation and/or a RuntimeException subclass that is thrown when this occurs, and a throws declaration on the setProgress and setMax signatures.

Thanks a lot for this awesome library. Is there anyway we can animate the ppvImage just like we animate or make progress for progress fill color. Right now the image is drawn directly. Any hint would be great. Lastly great work

from code: "startAngle start angle in degrees"

It's not clear to me how this is "human readable". Maybe I'm making a big geometry mistake in asking this question, but here goes ;)

1. Is it not the natural common-sense thinking that the value of an angle should be 0..360?
2. Is there some kind of multiplication going on to account for screen density? Should the factor be adjusted/variable?
3. Comments could explain home/origin position? is it at 12-o'clock or 3-o'clock?

The sample application uses 720 as a value. Currently line 48 of MainActivity.java code. It just doesn't seem intuitive to me why that ends up at the 3-o'clock position of a pie... for multiple reasons given. Would it not seem more like this is 90 using a compass?

Thank you for the code and time.

This pull request allows drawing an image in the background instead of just specifying only a background color. A background image takes precedence over a background color.

The background image is not rounded by this pull request, but you may set an RoundedDrawable found in the RoundedImageView library.