You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that using the TabControlEx creates 2 instances of the first ContentTemplate.
I have an example and hopefully not too complicated repo of this issue. Please forgive me if my coding is the problem, however, I believe I have created a fairly standard TabControl ViewModel project.
The project creates an ObservableCollection of ViewModels and uses a TemplateSelector to find the datatemplate as indicated below.
In MainWindow.xaml I have the following TabControlEx implementation and normal TabControl implementation. You can just change over to see the difference;
If you put a break on the creation of the UserControl BrowserTabItemUC and then use either the Standard TabControl or TabControlEX you will see that TabControlEX creates 2 instances of the usercontrol, even though only 1 ViewModel was created and added to the TabControls TabCollection.
The text was updated successfully, but these errors were encountered:
Describe the bug
It appears that using the TabControlEx creates 2 instances of the first ContentTemplate.
I have an example and hopefully not too complicated repo of this issue. Please forgive me if my coding is the problem, however, I believe I have created a fairly standard TabControl ViewModel project.
The project creates an ObservableCollection of ViewModels and uses a TemplateSelector to find the datatemplate as indicated below.
In MainWindow.xaml I have the following TabControlEx implementation and normal TabControl implementation. You can just change over to see the difference;
If you put a break on the creation of the UserControl BrowserTabItemUC and then use either the Standard TabControl or TabControlEX you will see that TabControlEX creates 2 instances of the usercontrol, even though only 1 ViewModel was created and added to the TabControls TabCollection.
The text was updated successfully, but these errors were encountered: