Thanks for the link, it has helped explain where to start. I guess my issue is that I was using a TabControl that was getting bound to a dynamic collection of IScreens and each TabItem was being created dynamically for each screen as opposed to in Rudi's
example where he hard-coded two named buttons in place with two known screens.
Using a tab control, I can't for the life of me work out how to monitor the switching of tabs and have actions invoked at that point along with switching to the new screen.
I tried manually binding the SelectedItem of the TabControl to a property in the ViewModel, but am not sure how to get the framework to Invoke an action with a fully wired up ActionExecutionContext with the Source set to the TabItem that was just selected.
I then tried ditching TabControls altogether and using Buttons like in Rudi's example, but am doing a lot of jumping through hurdles now to try and dynamically display buttons based on the screens that are available in the dynamic collection that I am populating.
Has anyone else had any success in using TabControls as a Conductor and performing actions when switching between screens?