NavigateToggle does not locate the appropriate Navigation context about fuselibs

[mortoray]

@kristianhasselknippe Yes, that's why I'm leaving this issue open as a defect. The context can be easily determined from the target page.

[mortoray]

Target here is the target page for NavigateToggle, but you also need to specify the navigation context. With EdgeNavigator this is a bit tricky since it isn't a navigation object itself. But, if really needed you can do:

                <MainContent ux:Template="mainContent" sideMenu="sideMenu" edgeNav="edgeNav" />

And then:

<Page ux:Class="MainContent">
    <SideMenu ux:Dependency="sideMenu" />
    <EdgeNavigator ux:Dependency="edgeNav" />

    <Button Text="Show menu" Navigation="{Property edgeNav.Navigation}">
        <Clicked>
            <NavigateToggle Target="sideMenu" />
        </Clicked>
    </Button>

</Page>

It's possible to put the context directly on the toggle as well:

        <NavigateToggle  NavigationContext="{Property edgeNav.Navigation}" Target="sideMenu" />

This issue is now for making the navigation context implicit if a Target page is provided. Though I'm uncertain of priority since I don't think this is a good way to do things. I find it much cleaner to expose a Open, Toggle or Close UserEvent that do this. The lower-level UX shouldn't be so tightly bound to the high-level objects.

[mortoray]

This issue is likely part of a bigger EdgeNavigator cleanup. It suffers from many small problems now. Search the old issue system.

[kristianhasselknippe]

@mortoray: Could NavigateToggle just use the navigation context of the element it is working on?