Hi,
I have a line chart that is updated frequently and after a while, for some users, I get an ArgumentOutOfRange exception. This is my stacktrace:
---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index') at System.Collections.ArrayList.get_Item(Int32 index) at Infragistics.Controls.Charts.CategoryAxisBaseView.GetValueLabel(Double value) at Infragistics.Controls.Charts.AxisAnnotationFrameManager.UpdateAnnoations(Object owner, AxisAnnotationFrame frame, Boolean modified, Dictionary`2 annotationPools, List`1 currentAxes, Boolean forceAxisUpdate, Int32 xFixedPrecision, Int32 yFixedPrecision, AxisFormatLabelEventHandler xAxisFormat, AxisFormatLabelEventHandler yAxisFormat) at Infragistics.Controls.Charts.CrosshairLayer.UpdateAnnotations(CrosshairLayerFrame frame, Boolean forceAxisUpdate) at Infragistics.Controls.SeriesViewer.BeforeContentRefresh() at Infragistics.Controls.Charts.ChartContentManager.DoRefresh()
I found this post:
https://ko.infragistics.com/community/forums/f/ultimate-ui-for-wpf/119679/xamdatachart---autoscaling-yaxis-and-other-questions
Point 7 in the first answer seems to describe my problem. Is there any update on this issue?
BR,
Hilma Maria
Hello Hilma,
Thank you for your post on this matter.
I have been investigating into the behavior you are reporting, and it appears that the development issue with ID 261623 for the exception logged on the other forum thread you have linked has been fixed. This was fixed in an early version of 2019.1 and a late service release for version 2018.2 in the Infragistics for WPF toolset, and appears to have been tested and verified as fixed against versions 18.2.20182.276 and 19.1.20191.64. Which version of the Infragistics for WPF toolset are you using?
Please let me know if you have any other questions or concerns on this matter.
Hi Andrew, I am using version 20.1 so the problem must be somewhere else. Thanks for the answer.
Thank you for your update on this matter.
Do you have any additional information or perhaps an isolated sample project that demonstrates the issue you are seeing so I may be able to reproduce it on our end and have it fixed if it still exists in the latest versions of the toolset?