Hi,
I am using a xamDataGrid where in each row I display text on multiple lines which needs follow these conditions.
The way is currently working is that we adjust the MaxHeight for each record whether the control's size or the records in view changed.
Everything worked fine until we upgraded from Infragistics V13.1 to InfragisticsV14.2.
After the upgrade, we started to see a big blank space in our control where we should see records the first time the control is displayed. If we start scrolling down, the missing records magically appear and everything looks fine afterwards.
Do you know if any changes were made around RecordsInViewChanged that would impact what we are doing? Is there a way to force a refresh for the records that should be in view after adjusting the record's heights?
Thanks,
Related to my first post, I set the CellMaxHeight and CellHeight of the FieldSettings the same height when initializing my grid.
fieldLayout.Fields["text"].Settings.CellMaxHeight = MaximumDisplayLines * DefaultCellHeight;
fieldLayout.Fields["text"].Settings.CellHeight = MaximumDisplayLines * DefaultCellHeight;
When RecordInViewChanged is triggered, I loop through the Records in View to adjust the height.I am actually adjusting the maxheight of the recordPresenter and not the height of my field which might be the problem.foreach (DataRecord dataRecord in _ReportViewGrid.GetRecordsInView(false)) { RecordPresenter recordPresenter = RecordPresenter.FromRecord(dataRecord); ... recordPresenter.MaxHeight = maxHeight); ...}
I did try to change the height of the field doing the following, but it doesn't change anythingCellValuePresenter.FromCell(dataRecord.Cells[textFieldName]).Height = maxHeight;
Please let me know what else I could try.
Hello,
Thank you for your post.
I have been looking into it the code snippet and details you have provided. I created a sample application based on your scenario and code snippet. I tested this project with the RTM and latest Service release of 14.2 and I could not managed to reproduce the behavior that you have described. If you are not able to reproduce the issue with the attached sample application, would you please modify it with the functionality, that you are using, so it reproduces the issue. This way I would be able to further investigate this for you and provide you with more detailed information on this matter.
Looking forward to hearing from you.