Hi Peter,
I believe I am not fully understanding you question.
The navigation functionality you are describing of "activating an existing view based on the navigation parameters or injecting a new one if it does not exist" is already supported by Prism's navigation API as out of the box. You can find a description of this in the following section of the documentation:
Hence, you would only need to adapt the MdiContainer control to a region (like with your region adapter) and sync the Views and ActiveViews collections of the region with the visual state of the corresponding controls (for example, the non active views could be shown as minimized MdiChild and the active ones as opened). Which type of region are you using in your region adapter? ( Region, SingleActiveRegion, AllActiveRegion, etc)
Thanks,
Damian Cherubini
http://blogs.southworks.net/dcherubini
I believe I am not fully understanding you question.
The navigation functionality you are describing of "activating an existing view based on the navigation parameters or injecting a new one if it does not exist" is already supported by Prism's navigation API as out of the box. You can find a description of this in the following section of the documentation:
Hence, you would only need to adapt the MdiContainer control to a region (like with your region adapter) and sync the Views and ActiveViews collections of the region with the visual state of the corresponding controls (for example, the non active views could be shown as minimized MdiChild and the active ones as opened). Which type of region are you using in your region adapter? ( Region, SingleActiveRegion, AllActiveRegion, etc)
Thanks,
Damian Cherubini
http://blogs.southworks.net/dcherubini