-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed MVVM Light #68
Conversation
0d143c3
to
19dc6f0
Compare
Removed the MVVMLight package as it is deprecated and added the Microsoft.Toolkit.Mvvm package as the successor. Some implementations had to be redone as MVVM Toolkit didn't provide a drop in replacement. An example for such case is the clearing/ unregistering of a viewmodel. I have added a method in the code behind of the main page that checks if it will navigate to the login page. If that is the case, it clears the navigation cache resulting in all cached pages being cleared (except for the pages using the 'required' navigation cache mode). The reason I added the cache mode enabled to the main page is so that users don't have to navigato through their directories after navigation back to the main page after every navigation.
19dc6f0
to
bc5c4e3
Compare
On master, at step 4, the volume slider is at 100, while this branch has a regression where the slider goes to 0 even though there is audio playing. |
I can reproduce this. Yes this seems to be a regression in the way how the VM is kept or not kept in memory or something. |
With MVVMLight, the static volumeUpdated was initialized to false on every navigation action to the page. With the new navigation, the static volumeUpdated actually held it's value which resulted in the volume not being updated after navigating to the page for a second time. This has been fixed by making the variable not static, so it is initialized every time correctly. Also added an assertion to self-document this, and added clarification comment.
77158d9
to
fce3d53
Compare
fce3d53
to
57cc720
Compare
Removed the MVVMLight package as it is deprecated and added the Microsoft.Toolkit.Mvvm package as the successor. Some implementations had to be redone as MVVM Toolkit didn't provide a drop in replacement. An example for such case is the clearing/ unregistering of a viewmodel.
I have added a method in the code behind of the main page that checks if it will navigate to the login page. If that is the case, it clears the navigation cache resulting in all cached pages being cleared (except for the pages using the 'required' navigation cache mode). The reason I added the cache mode enabled to the main page is so that users don't have to navigate through their directory, after navigating back to the main page after every navigation.
Reference: #66