UXTabControl

jimmyps — Wed, 16 Feb 2011 23:47:40 GMT

Hi Ross,

Using the event handler in MVVM application is not recommended. You can easily capture the selected tab in your VM through the SelectedIndex property of the UXTabControl. For instance, "SelectedIndex={Binding MyVM.SelectedTabIndex}"

In your case, the EventTrigger is treated as a content and thus a tab is created to encapsulate the content, which is no longer needed when you used the correct MVVM design pattern. The "content encapsulation" complies with the ItemsControl concept in which it allows you to host any UIElement in the control.

Please let me know if my suggestion works for you, or if you have specific reasons to use EventTrigger.

Hope this helps,
Jimmy

UXTabControl

rasmister — Wed, 16 Feb 2011 09:57:38 GMT

I was attempting to add a SelectionChanged event handler in XAML and determine which tab was being selected in my VM. When I add it to the UXTabControl structure, it thinks my EventTrigger is a tab and displays a tiny tab, and if you click on that tab it throws an exception. Can you please verify that you can actually add an eventtrigger to the UXTabControl and provide me with an example of how you did it?

Thanks,

Ross

Intersoft Community - ClientUI - UXTabControl

UXTabControl

UXTabControl