The XamDataGrid will throw a StackOverflowException when a user attempts to 'shift-select' virtualized rows. To reproduce, follow steps something like these: Select a row, scroll that row out of view, select another row with shift key held down, scroll that row out of view, select another row with shift key still held down.
I first noticed this with version 1 and see that it has not been fixed in the current release of v2.
A StackOverflowException bug obviously renders the component completely unusable in a production app. so hopefully this will be fixed asap.
"zmorris" wrote in message news:14849@forums.infragistics.com... The XamDataGrid will throw a StackOverflowException when a user attempts to 'shift-select' virtualized rows. To reproduce, follow steps something like these: Select a row, scroll that row out of view, select another row with shift key held down, scroll that row out of view, select another row with shift key still held down. I first noticed this with version 1 and see that it has not been fixed in the current release of v2. A StackOverflowException bug obviously renders the component completely unusable in a production app. so hopefully this will be fixed asap. http://forums.infragistics.com/forums/p/2263/14849.aspx#14849
Joe,
Thanks,
Zac Morris
The reason is lazy loading a control fails when you use the binded dataset; "Sample Data" is selected for use. I know a bit about lazy loading controls and a stack overflow may occur if the records are not loading correctly, the code is making assumptions about the record count, or the records are already loaded. In the Behavior Context Menu under the Properties Window in Visual Studio, the CellContainerGenerationMode set the propery to "PreLoad", on the RecordLoadMode property set it to "PreloadRecords". Set theScrolling Mode to "Immediate". This should resolve the lazy loading problem. The grid does need to be reviewed during demo mode or using the default recordset.