Does not support multiple frames about template10 HOT 6 CLOSED

Are you requesting support for multiple Frames?

from template10.

Hi Jerry! Well, I was working to one of the project templates recommended/built by MS: “NavigationMenuSample” that uses an AppShell and then sub-pages for content all in another frame. It seems a sensible approach, so yes support for multiple frames would be fantastic and make the Template10 very robust. Thank you!

From: Jerry Nixon [mailto:[email protected]]
Sent: 02 July 2015 07:40
To: Windows-XAML/Template10
Cc: Tim Charters
Subject: Re: [Template10] Does not support multiple frames (#4)

Are you requesting support for multiple Frames?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-117924745.

from template10.

Okay. Will just need a second invocation of the navigation service. Probably easiest to subclass the bootstrapper. Can you send me a link to the sample so I can understand the use case?

Best regards,
Jerry Nixon

Sent from my Windows Phone.
Please forgive typos and brevity.

from template10.

Awesome, thanks very much Jerry! Here is a link to the zipped sample, unedited, on my OneDrive. This doesn’t implement Template10, it is just a navigation sample.

From memory of when I looked at this I think you’ll need to make sure the new Bootstrapper contains a collection of NavigationService, as I think currently it forces the app root frame for its single reference. From there a suspend event can loop through the navigation services and save all the state just the same – except maybe with ID dependent keys to prevent accidental overwriting… you’re the pro, though! ☺

https://onedrive.live.com/redir?resid=256A7AAE20E85461!57906&authkey=!ALrhBZqulLbYDLY&ithint=folder%2czip

from template10.

If additional windows are going to be created, you need multiple cached dispatchers too

from template10.

You're right. Well need to move Dispatch from Bootstrapper into Frame façade, I think. This is pretty much an edge case but I think it can be worked in without creating any new implementation complexity. Models that cross frames will potentially throw cross thread exceptions in their property changed events of both frames data bind to the same property. Developers will have to be responsible for that on their own. Synchronizing through messaging would likely be how I would solve that. But that's an edge case of an edge case. Still, it would work.

Best regards,
Jerry Nixon

from template10.