Emil Alipiev
Emil Alipiev
"FreshTinyIoC.TinyIoCResolutionException: Resolve failed: LoginPageModel" doesnt necessarily mean that it is freshmvvm problem. Your page cannot be resolved because you have another error on your page. if you read the stacktrace...
nope it is not. popup doesnt resolve a pagemodel. it needs to be inhereted from freshbasepagemodel. why would you need something like that? do you want to get a value...
You can check within issues of rg popup github. There is the solution described there
You dont have use default themedmastedetaiilnavigationcontainer class from freshmvvm. you can create a new one and do whatever you want with it. it is totally independent implementation than freshmvvm itself....
Are you sure with that? did you profile it? i have this usage also very often and i am seeing that pages are removed without from the stack(not sure about...
if your theory is correct, it will be enough to extend ``` /// /// Remove specific page/pagemodel from navigation /// public void RemoveFromNavigation (bool removeAll = false) where TPageModel :...
Earlier I made same ticket but I think either this is hard or take so much time to implement, it wasnt implement. But you can always see the reason in...
what is the status today? can we not fix it?
@masonyc is is something related to this issue? https://github.com/rid00z/FreshMvvm/issues/188
Did you check your output window? you will have more information there. you have a mistake in your xaml or your viewmodel. it is not freshmvvm related i believe.