[ Originally posted on the "Chart" forum but actually this issue happens with ChartView ]
I am still in the process of evaluating
the Telerik WPF package. Everything was OK with the Chart component
until I found this problem.
When loaded with plenty of data, the chart crashes with the following exception :
Decimal too big or too small
at System.Decimal..ctor(Double value)
at System.Decimal.op_Explicit(Double value)
at Telerik.Charting.LinearAxisModel.<GenerateTicks>d__0.MoveNext()
at Telerik.Charting.AxisModel.<Delay>d__1e`1.MoveNext()
at
Telerik.Charting.AxisModel.TryBuildNonOverlappingTicksAndLabels(Boolean
buildLabels, ValueRange`1 zoomRange, Boolean allowOverlappingLabels)
at Telerik.Charting.NumericalAxisModel.ChooseActualRange()
at Telerik.Charting.NumericalAxisModel.BeginMeasureCore(RadSize availableSize)
at Telerik.Charting.AxisModel.MeasureCore(RadSize availableSize)
at Telerik.Charting.AxisModel.Measure(RadSize availableSize)
at Telerik.Charting.NumericalAxisModel.Measure(RadSize availableSize)
at Telerik.Charting.CartesianChartAreaModel.AxisStack.Measure(RadSize availableSize)
at Telerik.Charting.CartesianChartAreaModel.PrepareAxesStacks(RadSize availableSize)
at Telerik.Charting.CartesianChartAreaModel.ArrangeAxes(RadRect availableRect)
at
Telerik.Charting.ChartAreaModelWithAxes.UpdateAndArrangeAxes(SeriesByAxesTuple
seriesByAxes, RadRect availableRect, RadRect& seriesRect)
at Telerik.Charting.ChartAreaModelWithAxes.ArrangeOverride(RadRect rect)
at Telerik.Charting.ChartNode.Arrange(RadRect rect, Boolean shouldRoundLayout)
at Telerik.Charting.ChartAreaModel.Arrange()
at Telerik.Windows.Controls.ChartView.RadChartBase.UpdateChartArea()
at Telerik.Windows.Controls.ChartView.RadChartBase.CallUpdateUI()
at Telerik.Windows.Controls.ChartView.RadChartBase.OnInvalidated()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object
source, Delegate callback, Object args, Int32 numArgs, Delegate
catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32
msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object
source, Delegate callback, Object args, Int32 numArgs, Delegate
catchHandler)
at
System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority
priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at System.Windows.Application.Run()
Known problem? Any workaround?
1 Answer, 1 is accepted
It seems that I just answered your question in the thread you mentioned. I will ask that we keep the communication in a single forum (instead of 2) so that it is easier to follow a conversation. Thank you for understanding.
Regards,
Petar Marchev
Telerik