Hello,
when I add set following properties RecordContainerGenerationMode="Virtualize" RecordLoadMode="LoadOnDemand" to XamDataGrid and try to use vertical scroll bar for page down bit faster it crashes the app. How ever if I remove RecordContainerGenerationMode="Virtualize" RecordLoadMode="LoadOnDemand" and scroll it wont crash.
Please help me out, do I making anything wrong?
Thanks,
Mahesh
Hello Mahesh,
I cannot reproduce that, especially, when the ScrollingMode of the grid is deferred. Is it possible to provide a sample that reproduces this issue?
Hello Alex,
I changed scrolling mode to deferred still I see same exception and crash. Below is the code, on load of window I am fetching eventlogs data and binding ito xamdatagrid.
<ig:XamDataGrid RecordContainerGenerationMode="Virtualize" RecordLoadMode="LoadOnDemand" ScrollingMode="Deferred" IsGroupByAreaExpanded="True" Theme="Office2k7Blue" x:Name="eventLogsGrid"/>
Following are the environment on which I am testing.
Infragistics controls: 8.2.20082.2001
win xp sp3
.net framework 3.5 sp1
Note: once I remove below properties, it works fine no crash.
RecordContainerGenerationMode
="Virtualize" RecordLoadMode="LoadOnDemand" ScrollingMode="Deferred"
Thanks
I tested this with the latest Service Release for 8.2 and it is working as expected. Please install the Service Release. You can find it in your Keys & Downloads in our website.
If the problem still exists, please contact the developer support on this link.
Hi,
I experience the exact same issue. Try scrolling in this order, with at least 200 elements:
1. scroll to about 1/3 of the way down the list
2. scroll to about 2/3 of the way down the list
3. scroll to about 3/4 of the way down the list
My XAML is:
<igDP:XamDataGrid x:Name="mTable" RecordContainerGenerationMode="Virtualize"/>
The only difference may be that I am binding to a DataSet. I'm using 3 columns, 200 rows, but the data set size does not seems to create or prevent the defect when I change them.
Please make sure you have the latest Service Release installed for 8.2 as this issue has been resolved with it. If the problem still exists, please contact the developer support on the link from the previous post with a sample that reproduces this issue.