Hello,
I was using the version 2009.3 without any problem, but I switched to the latest version and I'm now getting this error while running:
"cannot be called with NaN values in availableSize
telerik.windows.controls.charting.linearSeriesPanel.measureOverride (size availableSize)"
Is there a fix for this?
Kind regards
4 Answers, 1 is accepted
0
pekkah
Top achievements
Rank 1
answered on 17 Mar 2010, 10:34 AM
I actually just finished sending a support ticket on this same issue.
Seems that the latest version if very buggy. I've gotten few serious issues which were not happening in the previous version.
Sorry for the whine instead of trying to give answer.
Seems that the latest version if very buggy. I've gotten few serious issues which were not happening in the previous version.
Sorry for the whine instead of trying to give answer.
0
KVA
Top achievements
Rank 1
answered on 17 Mar 2010, 11:55 AM
No problem, I'm glad someone else has the same error as me. I hope it will be fixed soon.
0
Hi guys,
We will need some more information about the specific scenario when this issue occurs. A sample project would be highly appreciated. Thanks.
Best wishes,
Velin
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
We will need some more information about the specific scenario when this issue occurs. A sample project would be highly appreciated. Thanks.
Best wishes,
Velin
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
pekkah
Top achievements
Rank 1
answered on 18 Mar 2010, 02:04 PM
Forgot to provide the fix for this issue.
There is a known bug when using AxisX Min, Max, Step values. You should use .AddRange instead.
This fixed the problem for me.
There is a known bug when using AxisX Min, Max, Step values. You should use .AddRange instead.
This fixed the problem for me.