On second thought, I'm not sure if that would be the best approach. One workaround at this point could also be to use PubSubEvents to notify the ViewModel for the parent region that a child view would like to become active, and leave it up to that parent ViewModel to do the activation. This may be better overall because there may be transient state in the current view for something like a TabControl where letting a child take control of the navigation by demanding it become active may be the wrong thing to do. The better way is to use the RequestNavigate means of activating an appropriate view within a region. That can be called from anywhere in a loosely coupled way, and leaves the views that are participating in the region in control of things like should the current view be navigated away from.
↧
