I have attached a project which demonstrates a possible bug. I am using XamWebGrid 10.1 with ColumnLayout. In the child level I am using a Template Column with a HyperLinkButton. If you start scrolling down you will get an error.
Hi,
Thanks for the sample, it was very helpful.
Basically whats happening is, we use a generated key to determine how a cell should be recycled. However, you've apparently managed to figure out the combination of the key and break recycling :)
B/c you have a column with the same key and the same parent columnLayout key, the wrong control gets returned and the recycling basically shows the wrong cell.
I think i can adjust this to be more unique. As a workaround for now, i suppose you can use a UnboundColumn. Assuming you're not going to be using any data operations such as sorting on the column that should be an easy way around the issue, as you can use any key for an UnboundColumn.
-SteveZ
Here is the updated project. I switched my columns at the parent level to be Template Columns and the error went away, however if you start scrolling down the grid some of the HyperLinkButton are not appearing at the 3rd Level. Below is a sample of how the data should appear on the screen.
-- Country---- State 1------ County 1 (this should be a link)------ County 2 (this should be a link)------ County 3 (this should be a link)---- State 2------ County 1 (this should be a link)------ County 2 (this should be a link)------ County 3 (this should be a link)
This issue is now resolved in the latest service release for NetAdvantage for Silverlight 2010 Vol. 3, build 10.3.20103.2159.
This service release is available under your account at the Infragistics Website. To download the service release, log in to ‘My IG’ and select ‘Keys & Downloads’. Select the NetAdvantage tab and then click on the product name. The available service releases should now be listed on the page underneath the tab control.
Please let me know if you have any further questions or concerns about this matter.
I've created a private case for you so that you can track the status of the fix Steve made and also be notified when it is available in a service release. To access the case, log in to ‘My IG’ and select ‘My Support Activity’.
Thanks for the update Steve.
Yes, its the same issue in 10.2 and 10.3
Although i have a fix for it so it will be addressed in the next SR.
Is this issue in later versions such as 10.2 or 10.3? Something worth investigating.