Hello,
We encounter a big problem when using sub bands in xamGrid. If a sub band needs a scrollbar, the xamGrid crashes the whole silverlight application each time you try to move the scrollbar.
The error is:
System.ArgumentoutOfrangeException: Index was out of range. Must be non-negative and less than the size of the collection.
I have attached a solution to demonstrate this problem.
The version of infragistics control used to reproduce the problem is 11.2.20112.2045.
Thanks for your quick answer, this is a really big blocking problem for us.
Pierre
Hello Elena,
I installed the release and everything is working now.
Thank you for your support.
Hello Pierre,
The service release containing the fix for your issue is out, you can download it from: https://ko.infragistics.com/Membership/Default.aspx?panel=Downloads#Downloads
I'd be glad to receive a feedback on the outcome.
To ensure that this will receive attention, I have created a case in our support system for you with number of CAS-80631-MB253R and I have linked it to the issue with id of 98448 .The next step will be for a developer to review it and offer a fix, or other resolution.
I will update you with any new information after the review. You can also continue to send updates to this forum thread.
You can view the status of the development issue connected to this case by going to the “My IG” tab on our website, hovering to the "My Support Activity" dropdown and selecting the "Development Issues" tab.
Please let me know if you need more information.
Thanks Nikola,
You're right, this is not really a solution, but I will use it for now. I will wait the middle of January for the correction.
Thanks for your help.
Hi pierreylieff,
That seems to be a bug, because of the column that you are having in the main layout of the grid with Width = "*". Change it to Auto or to specidic size and it won't be reproducible , but that could be only temporary solution for you. I have created a bug for you and will contact the DS team to link it with a case, so that you are notified when the bug is fixed. That bug should be fixed at the middle in January! Hope that helps!
Regards,
Nikola.