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.
The sample application that you provided is not exactly what we have to do, but I believe I have been able to fix my display issue by setting to false the AllowCellVirtualization property for my field. I don't think I require more assistance at this time.
Thanks.
Could you tell me if setting AllowCellVirtualization to False for some fields would impact the overall performance of the grid or if the performance should remain the same?
Hello ,
Thank you for your feedback, I am glad that you have managed to resolve your issue.
I have been looking into your question and it is depending on the number of your visible fields. If you had only visible fields or only several invisible and you turn off cell virtualization , probably this would not impact on the performance of your grid. I don't recommend turning off cell virtualization if you have a lot of fields. You can take a look at the following links from our online documentation, regarding more details about Cell Virtualization:
http://help.infragistics.com/Help/Doc/WPF/2015.2/CLR4.0/html/InfragisticsWPF4.DataPresenter.v15.2~Infragistics.Windows.DataPresenter.FieldSettings~AllowCellVirtualization.html
http://help.infragistics.com/Help/Doc/WPF/2015.2/CLR4.0/html/xamData_Cells_CellValuePresenters_and_Cell_Virtualization.html
You can take a look at the following links about more
The development issue with ID of 217163 has been fixed and it is available in the latest Service Release. You can download the Service Release by logging in our web site and then going to Account\My Keys and Downloads page.
Thank you for using Infragistics Components.
Sincerely,ZhivkoEntry Level Software Developer
Thank you for your using Infragistics Components.
I have investigated further this and I have logged this behavior with our developers in our tracking system, with an issue ID of 217163. I have also created a support ticket on your behalf with number CAS-171341-Q4R0J5 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.