You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
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
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: