Skip to content
This repository has been archived by the owner. It is now read-only.

In MvxCachingFragmentActivity, receiving a ViewModelRequest with different parameters of a frag already being shown, should trigger the ViewModel Lifecycle #112

Open
vvolkgang opened this issue Nov 10, 2015 · 1 comment

Comments

@vvolkgang
Copy link
Contributor

Currently, if we need to show a viewmodel with different parameters with a visible fragment, the process will be blocked somewhere inside MvvmCross. This needs to be changed in order to support the ViewModel lifecycle reload, so it receives the new parameters and by databinding, the current view should adapt to it.

@Cheesebaron Cheesebaron changed the title In MvxCFA, receiving a ViewModelRequest with different parameters of a frag already being shown, should trigger the ViewModel Lifecycle In MvxCachingFragmentActivity, receiving a ViewModelRequest with different parameters of a frag already being shown, should trigger the ViewModel Lifecycle Nov 11, 2015
@martijn00
Copy link
Contributor

Can you check again with the code after PR: #149 ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants