It seems that this behavior is hardcoded in the internal PolarAxisModel.
The method UpdateActualRange is overridden and the actualrange minimum is always set to zero.
However, in my case I have values that could be ranging e.g. from 9.95 to 10.05, or they could also be negative.
How to workaround this?
answered on 26 May 2014, 07:27 AM
You are absolutely right, the set minimum of the polar axis is disregarded and it is internally forced to a zero. This is because leaving the polar axis with a minimum different than a zero might lead to an unclear visual representation. However, I will ask that you provide us with some snapshots(drawings of some sort) that depict the output you need, so that we can consider changing this.
Currently we do not have any implemented work arounds for this. If this is a must in your application, we may be able to suggest something, but keep in mind that it will most likely be some heavy work, as this is not a built-in feature an you will have to fight the internal logic of the control.
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.