I'm experiencing a werid drawing problem when using the GroupBy feature in the xamWebGrid. This is version 2010.1 for Silverlight 3
Sometimes the label for the first groupby row seem to get hidden by a white rectangle. See attached screenshot:
The first row should say "Closing Documents" but it looks like a white rectangle is drawn on top of part of the row.
Not sure what the cause is. The grouping is set in XAML by using the IsGroupBy property for one of the columns. The following steps causes the issue:
1. Expand any of the rows.2. Collapse the same row again.3. Remove the control from the visual tree (e.g. by putting it on a tab control and switching tabs).4. Add the control to the visual tree again.
Our XAML code is pretty straighforward and it only happens when we use grouping. Everything else is fine.
Any ideas?
Hello,
This issue has been resolved in the latest service release, build 10.2.20102.2066.
I'm creating a private case for you for this issue so that I can link it to the development issue. This will allow you to track the status of the development issue and also you will be automatically notified once the fix is available in a service release.
Ok, thanks for the answer. We're planning on upgrading shortly so I guess we'll just have to wait for the service release.
You mentioned this is reported as bug 35275. Is there anywhere I can read that bug report (and others)? I haven't been able to find a link to any bug tracking system or similar anywhere on your site. Only thing I could find was a "Search Incidents/Bug Reports" in devcenter (after login on) but that just gives me an empty result list, regardless of search criteria.
Hi,
Yes, this is something we recently identified and will be in our next Service Release, however its something we could only fix for SL 4.
Whats happening is, when we recycle cells that should no longer be in view, we put them out of the screen, To keep performance up, we only arrange these cells once. However, when the xamGrid is taken out of the VisualTree and put back in, those elements that we originally arranged out of view, are back in view again.
However, there is no way for us to know about this. Or at least there isn't a way in SL3, in SL4 they added an Unloaded event, which lets us clean up all of the rows that were out of view, so that in the next Arrange cycle, we can arrange them out of view again.
The bug associated with this issue is: 35275
-SteveZ