Hello,
So I've noticed that on the first run of our application, clicking a record in the main grid somehow causes multiple records above that particular record to become selected. This also reassigns the active record to the top record in the stack of selections. I've managed to create a bare-bones example that works most of the time (in our actual application it is very consistent). What's supposed to happen is a user selects a record and the parent record appears above it in a separate grid. If no selection is made the parent grid collapsed.
In the stack trace, after setting the ParentRecords property, external code re-calls the Infragistics SelectedItemsChanged on the grid with the records above the original selection.
This bug has been a big thorn in my side for a long time, suggestions are much appreciated.
Thanks,
Danielle
Hello Danielle,
Thank you for your post!
I have been looking into it and into the sample application, that you have provided. When I unzip the attachment and try to run it a get an error message. Please find the message attached.
I have extracted the code, that is in the sample application, that you have attached to a newly created project and I was not able to reproduce this issue.
In order for me to be able to further investigate this matter for you, would you please provide me with a simple isolated runnable sample application, where the issue is reproducible?
Looking forward to hearing from you.
Gergana,
To simplify things I decided to just remove our NuGet packages. I was able to reproduce the issue with INotifyPropertyChanged. I've re-attached the sample project with this in place.
Hi Gergana,
I think the record that you click is irrelevant. Our application is full screen and might only have 10 records, so no scrolling would occur. I was able to verify this with the sample app if you just make the window a bigger size. Additionally, we need to be able to multi-select records for a multi-delete control.
The opacity might work, although it's not a very clean fix. This is a reusable grid class that we use across our application, and not all of the grids will be able to see these. It would be weird to have a giant blank space above the grid in these cases.
I have been looking into your post.
Currently the best approach, that I can suggest is to set the opacity for the XamDataGrid to a low number(for example 0.2 or 0.1). This way the grid would take the space, that it would need and it would slightly visible.
Please do not hesitate to let me know if you have any further questions on this matter.
I am just checking if you have any further question on this matter. Please do not hesitate to let me know if you do.
I think that covers it for now if there's not really a better solution than that. The team didn't really like any of the temporary solutions, so I think we will write it up as an Infragistics bug. Thanks.
Thank you for the feedback.