Is there built in support for disabling tab virtualization in the XamTabControl?
Jesse
No, that's all I needed, thanks. I would consider this a defect rather than a feature request. I won't be submitting this as an idea.
Hello Jesse,
I am just checking if you require any further assistance on the matter.
Hi Jesse,
Thank you for your reply. Currently we do not provide such kind of property which controls the virtualization of the XamTabControl. In order to achieve such kind of behavior by creating a TabItemEx for each object from your underlying data manually as the content of the TabItemEx has an UserControl as content. I am attaching a sample application(TabControlVirtualization.zip) that shows this approach.
You can submit a new product idea for creating such kind of property for future versions at http://ideas.infragistics.com.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
1. Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2. Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3. Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
That's not what tab virtualization is in this context. When a tab is changed the framework reuses the controls in one tab for the next and just changes the datacontext. You can see the behaviour if you use a bound collection for the tabs and subscribe to the loaded event for the control in the template, it will only fire once for the first control. What I would like to know is if the XamTabControl has a property to force instantiation of controls in a tab.
This stackoverflow question describes the issue : http://stackoverflow.com/questions/4993159/why-do-tab-controls-reuse-view-instances-when-changing-tab
The Telerik controls have such a property called "IsContentPreserved".
Thank you for your post. I have been looking into your question and currently we do not have a built-in property that could disable the virtualization of the XamTabControl.
You could try to set its ‘Width’ and ‘Height’ properties to “Auto” and place it inside ScrollViewer(or Canvas) in order to disable the virtualization.
Let me know, if you need any further assistance on this matter.