Angular Gauge Adjusts Upperlimit When Value Is Whole Number

[Mark Anthony]

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 May 30, 2012 by Mark Anthony

[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.

 

 

[Mark Anthony]

Thanks Sumedh.

[Guest Sumedh]

Thanks Sumedh.

 

[Steve Workings]

Any further news on when a fix will be available? It's been a few months now, and it's past time for my site to be displaying a correct chart.

 

Thank you.

[Guest Sumedh]

Hey,

 

We are still working on this issue.

 

We will update you on this, shortly.

 

Thanks for your time and support.

[Guest Sumedh]

Hi Steve,

 

This bug has been fixed now.

 

The fix will be available in the next service release.