I have a bit of a strange case,
I have a tab control.
And on each tab I have a grid.
Switching between these tabs is very slow.
You also end up with this in output window of visual studio every time you switch tabs:
System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='DataPresenterBrushKeys.GroupByAreaBackgroundHighlightKey'; ResourceKey.HashCode='36205315'; ResourceKey.Type='Infragistics.Windows.Themes.StaticPropertyResourceKey'
If you turn off the office2007 theme these mesages go away and it speeds right up.
Odd? Quite.
It took me some work to reproduce my problem in a test app but this is what I have found.
If you add XamGrids to the tab control directly, no problems (switching stays fast). If the grids get added through a Wpf data biding the this problem occurs.
Something like this for example : (Where 'View' ends up being a control with a xamlGrid on it.)
<Window.Resources>
<DataTemplate x:Key="ContentTemplate">
<ContentControl Content="{Binding Path=View}"/>
</DataTemplate>
</Window.Resources>
<TabControl Name="BoundTabControl"
ContentTemplate="{StaticResource ContentTemplate}">
</TabControl>
Any ideas? or should I be sending this one to support.
Hello,
I tried to reproduce this behavior. I was able to some extent but not all of it.
I really get these warnings in the Output, however, the performance does not change much. Probably I am missing something in the process of recreation.
If you have a working sample, please attach it here so I can look it in or contact directly developer support here.
Alex.
I am getting this problem also, was it ever submitted to development? In my case it's REALLY impacting performance.
I also seem to have this problem. I have tabs with DataTempalte being bound to the control which contains your grid. The output window also has "Infragistics.Windows.Themes.StaticPropertyResourceKey" no found errors :(
Thanks!
rmking: the issue is logged in our system and is currently in progress. You will be automatically notified when it is resolved.
warrenwnj: I have created a support case on your behalf and linked it to the same issue (17184) so you can be also notified.
Regards,
Yes we did submit the problem.
Our reference number is 17184
They are looking into it, but no progress yet. It has been upgraded to a development issue, and that is the last that I heard.