Sign in to follow this  
Mark Anthony

Angular Gauge Adjusts Upperlimit When Value Is Whole Number

Recommended Posts

Hi,

 

This is my first post here. Please pardon me if this I am not in the right category. All I need is just guidance on the usage and not necessarily to report a bug.

 

My Angular Gauge simply has the following properties

lower limit = 0

upper limit = 0.5

 

When the value of the dial is 0.01, it displays the gauge properly that is, range is 0 to 0.5

 

but when the value of the dial is 0, it auto adjusts the upper limit to 1.

 

I have done everything I can and tried almost all properties in the document. I thought it may have something to do with the value so instead of "0", I formatted it to "0.0" but it didn't solve the issue.

 

I may be missing something.

 

Thanks.

 

this is correct.bmp

adjusts to 1.bmp

Edited by Mark Anthony

Share this post


Link to post
Share on other sites
Guest Sumedh

Hi,

 

This is my first post here. Please pardon me if this I am not in the right category. All I need is just guidance on the usage and not necessarily to report a bug.

 

My Angular Gauge simply has the following properties

lower limit = 0

upper limit = 0.5

 

When the value of the dial is 0.01, it displays the gauge properly that is, range is 0 to 0.5

 

but when the value of the dial is 0, it auto adjusts the upper limit to 1.

 

I have done everything I can and tried almost all properties in the document. I thought it may have something to do with the value so instead of "0", I formatted it to "0.0" but it didn't solve the issue.

 

I may be missing something.

 

Thanks.

 

this is correct.bmp

adjusts to 1.bmp

 

 

Hi,

 

It has been identified as a bug.

 

We will update you on this as it will be fixed.

 

 

Share this post


Link to post
Share on other sites
Guest Sumedh

Hey,

 

We are still working on this issue.

 

We will update you on this, shortly.

 

Thanks for your time and support.

Share this post


Link to post
Share on other sites
Guest Sumedh

Hi Steve,

 

This bug has been fixed now.

 

The fix will be available in the next service release.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this