{"action":"opened","issue":{"url":"https://api.github.com/repos/PrismLibrary/Prism/issues/131","labels_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/131/labels{/name}","comments_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/131/comments","events_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/131/events","html_url":"https://github.com/PrismLibrary/Prism/issues/131","id":105452495,"number":131,"title":"[UWP] OnNavigatedTo and OnNavigatingFrom for shell in case of a SplitView","user":{"login":"diego2k","id":4716265,"avatar_url":"https://avatars.githubusercontent.com/u/4716265?v=3","gravatar_id":"","url":"https://api.github.com/users/diego2k","html_url":"https://github.com/diego2k","followers_url":"https://api.github.com/users/diego2k/followers","following_url":"https://api.github.com/users/diego2k/following{/other_user}","gists_url":"https://api.github.com/users/diego2k/gists{/gist_id}","starred_url":"https://api.github.com/users/diego2k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diego2k/subscriptions","organizations_url":"https://api.github.com/users/diego2k/orgs","repos_url":"https://api.github.com/users/diego2k/repos","events_url":"https://api.github.com/users/diego2k/events{/privacy}","received_events_url":"https://api.github.com/users/diego2k/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-08T19:24:14Z","updated_at":"2015-09-08T19:24:14Z","closed_at":null,"body":"Hi, \r\ncurrently the solution for the SplitView is to give the PrismApplication another Frame which should be used for the navigation. The Problem is the shell may also have a state which has to be saved in case of a suspension. Because the shell is always visible the OnNavigatingFrom and OnNavigatedTo should be called every time a suspension happens. \r\nI think at the moment the only possibility to save the state of the shell is to use the Resuming and Suspending event in the App.xaml.cs which is not a really nice solution ... \r\nThanks"}}