Replies: 2 comments 3 replies
-
Here's a repository that shows the issue: https://github.com/HakanL/Uno-Navigate-Issue |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't know if this is related, but my finding is that when navigating to the same view model, but with different data, a new instance of the ViewModel is created (as expected), but the Page is just re-used with a new DataContext. That may be correct, it's just an observation that perhaps is related to the navigation stack. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have routes that has a single item like this:
and I navigate to a page that display menu items with this command:
And from here I can go further down the path, with the same call, but with a different
menuItems
instance. I can navigate down the menu perfectly fine, but when I'm let's say 2 levels down and callNavigateBackAsync
then I'm taken all the way to the top. It's like the different calls toNavigateViewModelAsync
doesn't take the data into consideration. How can I make sure all my calls to navigate with different data are added to the navigation stack?Beta Was this translation helpful? Give feedback.
All reactions