-
My |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
The One thing you might be able to do is: public class ParentViewModel : Conductor.Collections.OneActive<IScreen>
{
public AViewModel A { get; }
public BViewModel B { get; }
public ParentViewModel()
{
A = ...
B = ...
this.Items.AddRange(A, B);
}
} <TabControl SelectedItem="{Binding ActiveItem}" .....
<TabItem><ContentControl s:View.Model="{Binding A"}/></TabItem>
<TabItem><ContentControl s:View.Model="{Binding B"}/></TabItem>
</TabControl> (Untested). So, your ViewModels exist as properties of the parent (which you bind to from your |
Beta Was this translation helpful? Give feedback.
The
Conductor
classes all have special logic to activate and deactivate their children when appropriate. If you're not using this, you'll have to write that logic yourself.One thing you might be able to do is:
(Untested).
So, your ViewModel…