This repository has been archived by the owner on Feb 16, 2023. It is now read-only.
Region Default View #63
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds a DefaultView Attached Property for the RegionManager. When specified on a given Region the Region AutoPopulate Behavior will evaluate the value from the TargetElement and add/create the specified View and add it to the Region. This will occur prior to Prism's Page Navigation interfaces firing meaning that you can tie into IInitialize, or INavigationAware to pass the context to the ViewModel of the Region View. Note that this will accept a name, type or View instance.