I'm trying to create an UWP (Universal Windows App) application with C#. My problem is the Frame
control: If I use it without NavigationCacheMode = Required
, every time the user goes back, the page is not kept in memory and will be recreated. If I set NavigationCacheMode
to Required
or Enabled
, going back works correctly (no new page object) but if I navigate to another page from the same type, the previous page object is recycled and reused (no new page instance).
Desired behavior:
Is there a way to have the following behaviour with the original Frame
control (like in Windows Phone):
- Create new page instance on
Navigate()
- Keep the page instance on
GoBack()
The only solution I know is to create an own Frame
control but this leads to other problems (e.g.: missing SetNavigationState()
method, etc...)
Sample scenario:
Simple application example with three pages: TvShowListPage
, TvShowDetailsPage
, SeasonDetailsPage
.
TvShowListPage
is the entry page. After clicking on aTvShow
navigate toTvShowDetailsPage
.- Now in
TvShowDetailsPage
select a season in the list and navigate to theTvShowDetailsPage
. - If navigating back, the pages should stay in memory to avoid reloading the pages.
- But if the users goes back to
TvShowListPage
and selects anotherTvShow
theTvShowDetailsPage
gets recycled and is maybe in the wrong state (eg showing the cast pivot instead of the first, seasons pivot)
I'm looking for the default Windows Phone 7 behavior: Navigating creates a new page on the page stack, going back removes the top page from the stack and displays the previous page from the stack (stored in the memory).
Solution:
Because there was no solution to this problem, I had to reimplement all paging relevant classes: Page, Frame, SuspensionManager, etc...
The library MyToolkit which provides all these classes can be downloaded here: https://github.com/MyToolkit/MyToolkit/wiki/Paging-Overview
References:
- http://www.jayway.com/2012/05/25/clearing-the-windows-8-page-cache/: No good solution
- http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/88e6d1b3-1fa6-4ab4-a816-e77c86ef236f/: Implementing of an own Frame class is no solution as it doesn't work with
SuspensionManager