The rendering of the rows after the ObservableCollection loaded takes few seconds.
In the website it says you can render million rows in a second, it is only 30,000
I use a user control which groups and exsposes functionality of the sfDataGrid.
I provided an example project, I use some custom styles and I would like to know what could be the problem
to test the rendering, press the upper button and you will see the UI thread gets stuck for a few seconds.
Another thing, in the real world project the rendeting takes about 5-10 more seconds. Might be because additional styles and more columns are used?
The problem occurs even with virtualization enabled.
Thank you
Attachment: WpfApp2_8f190607.zip
Hi Idan,
Currently, we are analyzing your provided sample from our end. We will validate
and update you details on or before April 29, 2022.
We appreciate your patience until then.
Regards,
Vijayarasan S
Hi Idan,
We are still working on this. So, we need two more business days to validate
this. We will update with further details on or before May 4, 2022.
We appreciate your patience until then.
Regards,
Vijayarasan S
Hi Idan,
We have created bug report for the reported issue “UI not respond properly
while adding more number of records at runtime when ColumnSizer defined in
GridColumn of SfDatGrid”. We will fix this issue and include in our first NuGet
release on after the Essential Studio 2022 Volume 1 SP release.
You can track the status of this report through the following feedback link,
Feedback link: https://www.syncfusion.com/feedback/34645/ui-not-respond-properly-while-adding-more-number-of-records-at-runtime-when
Note: The provided feedback link is private, and you need to login to view this feedback.
However, you can temporarily avoid the reported problem by remove
the defined ColumnSizer in GridCheckBoxColumn of SfDataGrid. Please refer the
below code snippet,
|
<syncfusion:GridCheckBoxColumn MappingName="IsSelected" AllowSorting="False" AllowFiltering="False" AllowGrouping="False" AllowEditing="True" HeaderText="נבחר"/> |
Please find the sample in the attachment and let us know if you have any
concerns in this.
Regards,
Vijayarasan S
Hi Idan,
We regret for inconvenience.
We are unable to include the fix for this issue in our NuGet package which is released today. We will fix this issue and include it in our upcoming Weekly NuGet release scheduled on May 24, 2022.
We appreciate your patience and understanding.
Regards,
Vijayarasan S
Hi Idan,
We regret for the delay caused
We are unable to include the fix for this issue in
our NuGet package which is released today. We will fix this issue and include
it in our upcoming Weekly NuGet release scheduled for May 31, 2022.
We will let you know once it is released with the
fix. We appreciate your patience until then.
Regards,
Vijayarasan S
Hi Idan,
We deeply regret for the delay and inconvenience caused.
We are unable to include the fix for this issue in our NuGet package which is released today. We will fix this issue and include it in our upcoming Weekly NuGet release scheduled for June 07, 2022.
We appreciate your patience and understanding.
Regards,
Vijayarasan S
Hi Idan,
The Reported issue occurs due to the usage of “Column Sizer”
property. The Column Sizer behavior is measure the cell’s size based on the
cell’s content. It will measure for each and every cells in datagrid. We have
measured the size using FormattedText API. We have raised the query in GitHub
with same set of codes using FormattedText. As per the GitHub update if a lot of
work is done in the button click event handler then the button will remain in the last
drawn state(pressed state) until the process is completed. The delay in the
button’s state is expected for this number of iteration.
GitHub query link: https://github.com/dotnet/wpf/issues/6642
We will update you with details, once we get any proper solution from GitHub.
We appreciate your patience until then.
Regards,
Vijayarasan S
Hey, thanks for the reply
The issue is occuring also when the data fetching is async.
Hi Idan,
We have tried the suggested solution from GitHub. The reported problem still occurs. So, we have updated the further details in the GitHub link. We will update you with details, once we get any proper solution from GitHub.
We appreciate your patience until then.
Regards,
Vijayarasan S