Hi,
today i updated a project from 10.2.20102.2174 to 2207.
In my window I have several views in a XamDockManager.In one view I have a XamDataGrid which has a FieldLayout with a SummaryDefinition.Since the update I get a System.NullReferenceException when I try to open the view with an empty datasource.
The stacktrace end's with:
bei Infragistics.Windows.DataPresenter.GridViewPanelFlat.ArrangeHelper(UIElement visualChildElement, Dictionary`2 headerRecordMap, Boolean orientationIsVertical, Boolean isReverseLayoutForBottomFixed, Double extentUsedByLastItem, Double clipExtent, Size arrangeSize, Rect& arrangeRect, Double& recordIndent)
bei Infragistics.Windows.DataPresenter.GridViewPanelFlat.ArrangeOverride(Size finalSize)
The whole stacktrace is attached.
When I loaded the Infragistics Sourcecode, Visual Studio points to the file DataPresenter\GridViewPanelFlat.cs and the following line where headerRecordMap is NULL:
// JJD 1/24/11 - TFS63831// Make sure the header is removed from the map so it// doesn't get arranged out of viewheaderRecordMap.Remove(attachedToRecord);
Removing the SummaryDefinition from my FieldLayout avoids the exception but since it worked in 2174 it seems to be a bug.
HI DICOM201,
I was unabe to reproduce this issue using build 10.2.2207. I am attaching a sample project. Please feel free to modify it so that it replicates your issue.
Sincerely, Matt Developer Support Engineer
Hi Matt,
the only thing missing in your sample was a key in the FieldLayout.Adding "Key="{x:Type app:Person}"" brings the NullReferenceException.
I've attached the modified sample.
Sincerely,
Bastian
HI,
I am going to submit this issue for developer review.
Sincerely, MattDeveloper Support Engineer
HI ,
Currently this developer issue is in review.
I have no timeframe as to when it will be resolved.
I'm having the same issue using the summary row and a blank datasource and the latest service release. A workaround or fix needs to be produced ASAP. This is ridiculous.
This issue is killing me. It makes using summary rows unacceptable. The error causes your clients to just bomb out cursing you in the process. Its ashame that such a large bug was allowed out in the wild.