Hello,
We are using Infragistics 13.1 and having this issue from time to time using XamDataGrid.
Any ideas?
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Infragistics.Windows.DataPresenter.VirtualizingDataRecordCellPanel.GetFieldsInView()
at Infragistics.Windows.DataPresenter.VisibleDataBlock.Create(List`1 recordPresenters)
at Infragistics.Windows.DataPresenter.RecordsInViewHelper.ShouldProcessRecordManager(RecordManager rm, IList`1 fieldInfos)
at Infragistics.Windows.DataPresenter.RecordsInViewHelper.ShouldProcessInViewRecord(Record record, IList`1 fieldInfos)
at Infragistics.Windows.DataPresenter.AutoSizeFieldHelper.Calculate(RecordEnumeratorBase outOfViewRecords, AutoSizeCalculationFlags flags, RecordFieldList& recordFieldList, Boolean trackRecords, RecordsInViewHelper recordsInViewHelper)
at Infragistics.Windows.DataPresenter.AutoSizeFieldLayoutInfo.PerformAutoSize(Boolean isHorz, IEnumerable`1 autoFields, RecordCollectionBase records, Int32 recordManagerDepth, HashSet recordsSubset, Boolean increaseOnly, OperationType operationType, FieldAutoSizeOptions allowedOptions, RecordsInViewHelper recordsInViewHelper)
at Infragistics.Windows.DataPresenter.AutoSizeFieldLayoutInfo.ProcessPendingOperationsImpl(RecordsInViewHelper recordsInViewHelper)
at Infragistics.Windows.DataPresenter.AutoSizeFieldLayoutInfo.ProcessPendingOperations(List`1 pendingAutoSize, RecordsInViewHelper recordsInViewHelper)
at Infragistics.Windows.DataPresenter.DataPresenterBase.ProcessPendingAutoSizeOperations()
at Infragistics.Windows.DataPresenter.DataPresenterBase.OnPerformFieldAutoSize(Object parameter)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
Thank you for your post. I have been looking into it, but since this is not a known issue I cannot conclude what can cause it, so if you still haven’t resolve thus, could you please send an isolated sample project, where the issue is reproduced, so we can investigate it further for you.
Looking forward for your reply.
Looks like it's been an issue before:
http://dl.infragistics.com/community/wpf/ReleaseNotes/WPF_ReleaseNotes_12_2_SR_December_2012.pdf
Can you confirm that this defect has actually been fixed? Which version it was fixed in and what the fix was?
Cheers,
Nick.