Hello community!
The datagrid is used to display production information. At the moment around 1600 rows are loaded and displayed. For user convenience, multiple converters and styles are used for background color and for displaying the values. To enhance the filter experience, all fields are set to "EditAsType="{x:Type sys:String}" so that the filter "contains" could be used.
In principle, the whole thing works well and quicky, but there are sporadic situations when "changing" or "deleting" filters that the entire application hangs and the window "..is not responding" is displayed.
All column widths are set (no auto or *)A list with suppressed events has been addedTheme is set to "Office2013"Edit is not allowedGroup, Summary and Filter is allowedDataRecordsizingMode is "fixed"AutoGenerateFields is "false" UseNestedPanels is set to "false"DataSource is an ObservableCollectionIs there a setting for the XamDatagrid to enable logging? I would like to know what is happening and if i can turn on logging, i would not have to check all the time if the problem is now occuring.
Best regards
Andreas
Hello Andreas,
Thank you for your update on this matter.
It may be better if you are editing as string to just insert string properties to the XamDataGrid as this will prevent the internal conversion that would need to happen between editing as a string to your underlying data type.
I will continue to monitor this forum thread while I await your update about point 3 if there are errors displayed.
It is also worth noting that version 21.2.20212.9 is the base version of 21.2. There have since been 4 service releases since this version, which you can download from your account, and the most recent service release (21.2.20212.158) was the final one for version 21.2. It may be worth upgrading to the latest service release on this matter to see if this issue is fixed there.
Please let me know if you have any other questions or concerns on this matter.
Hello Andrew!1. Used Version: 21.2.20219.9
2. Would it be better if we insert string properties into the class which are then displayed instead of the EditAsType setting?3. I have to check if there are errors displayed.4. Creating an isolated sample is not possible at the moment. The problem does not happen very often. Thank you for the tip with the source code.
My team and I have done an initial review of this post, and I have a few questions for you on this matter. Would it be possible for you to please provide an answer to the following?
1. What is the specific version of Infragistics for WPF are you targeting? For example, this number should look something like the following if targeting 2022 Volume 2: (22.2.20222.XXXX).
2. The EditAsType=”x:Type sys:String” seems a little bit risky to me at a first glance. Does this happen if this is not set?
3. Are you seeing any error messages in the Output window in Visual Studio when this UI hang is happening?
4. Do you have an isolated sample project you can share where this behavior is reliably reproduced?
Regarding “turning on logging” for the XamDataGrid, there is nothing on the control that you can use to do this. My best recommendation would be to download the source code from your account on the Infragistics website, as you would then be able to compile that and run against it. This may make profiling the performance issue easier as you would then have access to all of the internal APIs of the grid. You can download the source code after selecting the version of the product and the “Source Code” radio button in your account, here: https://account.infragistics.com/downloads.
Please let me know if you have any questions or concerns on this matter.