Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Very first setValueAnimated() invalidates min/max values. #14

Open
java-artisan opened this issue May 18, 2014 · 1 comment
Open

Very first setValueAnimated() invalidates min/max values. #14

java-artisan opened this issue May 18, 2014 · 1 comment

Comments

@java-artisan
Copy link

When using a dial with min- & max indicators, the minimum value is set from here the animation started. Which is wrong because such a value never was passed to the gauge.

@mcrossley
Copy link
Collaborator

This is how it is currently implemented. The min/max indicators are designed to take their values from the value supplied to the gauge. I know that typically when you first draw the gauge you may animate it up from a 'zero' value to the current value. In this case what I do is use the animation complete callback feature of .setValueAnimated() to enable the minimum pointer and set its value after the initial animation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants