Hi,
XamDockManager is slow when it performs dock operations or changes the active Pane in a TabGroupContentPane...
I attach a sample, please click on each one of the W_ panes, then click W1 and you will see that the content becomes blank and there is a delay showing the W1 content....
Then try to dock W2 to bottom and see the delay....
Each ContentPane contains a grid with no data and 30 columns....
PS
I use the latest Service Release..
In the application we develop this behavior is much more visible!!!
Regards,
Michael
I am facing the similar issue..any solution???
There is also this post,
http://community.infragistics.com/forums/t/58905.aspx
that states that a redraw of a UserControl occurs when switching tab pages.
I uploaded a modified sample with a tab control and the same tabs, the switch from each tab does not flicker (the content is not user control, it is just a xamgrid control)
Also when performing a dock operation , the content pane should not draw it's content because the operation is slow... just a rectangle should do the job...
Hello,
there is no answer from ig,
so are there any plans to improve performance for XamDockManager?
On a service release or on 11.2 ?
Michael,
Thanks for the samples. I can see the difference in behavior vis-a-vis the TabControl. I will communicate with you via the private support case you created and will post th eresolution here when that is determined.
Regrads,
Hello Francis,
thank you for your clarifications.
My point is that the performance of tab switching does not seem good, because of this.
Another major performance penalty is the drag operation... As i have mentioned in the private case, it would be much faster not to preview the change of the layout until the drop operation takes place.... Just show the Dock Hints and the performance benefit will show huge...
You could also make a Feature request for that too (make a setting not to preview the drag/drop operation )
Are there any plans of implementing the above requests? I need to use the dock manager in complex layouts, and performance is mandatory....
Hello Michael,
As we have communicated via private support case, the behavior we see here is by design. The MS tab actually waits for the new content to load before showing the new tab header becoming selected, while the Infragistics TabbedGroup immediately shows the selection changing, then displays blank content until it is loaded.
We have, at the recommendation of our Engineering group, logged Feature Request FR13475 for this behavior to be like that of the MS Tab control.
Thanks,