Oct 30, 2011 at 4:41 PM
Edited Oct 30, 2011 at 4:52 PM
I’m using the Navigation framework and I reached a point where I need to toggle between multiple views within a single screen. It seems more appropriate to use SubRegions as opposed to toggling between UserControls (in theory :)
Has anyone faced such scenario and kind to share some possible pitfalls?
I already noticed that the RegionContext can be bound only to Controls in the host region (e.g Dependency Property sources) and I think I can live with that.
However, my concern is about how SubRegions play with the Navigation Infrastructure
(e.g RequestNavigate(RegionNames.SubRegion … ??)