Thanks for that info.
I've been experimenting with some things and want to clarify.
It appears I will have to handle and implement code to activate all views from the nested view up through all parent views ultimately arriving at the top level view to make the nested view visible.
And, that there is nothing "built-in" to Prism that will do that for me?
For example:
- In my shell I have top level views as tabs, I can activate top level views easily to force them to become the visible tab (active) if they are not currently visible
- If I have a nested view inside one of these top level tabs but the top level tab is not currently visible (active), I have to activate every view from the nested view upwards ending with the top level tab view. If I don't, calling region.Activate(view) will succeed, but will not do anything to cascade activating parent views to the point they are actually visible.
Assuming I'm always starting from the nested view (it starts by receiving an event) and need to activate up the parent tree, I'll need a re-usable pattern so it will work in any injected/nested view combination. It simply needs to continually activate parent views until there are no more to activate. That should ensure the nested view will be visible to the user no matter where the request to view it came from.
Does that summarize it the way you are thinking it needs to work given my situation?