Added GlobalProviderState to ProviderManager property for easy binding #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
PR Type
What kind of change does this PR introduce?
What is the current behavior?
SwitchPresenter from WCT doesn't work well with the GlobalProvider state as it exists today. It is not possible to simply use
ProviderManager.Instance.GlobalProvider.State
because theGlobalProvider.State
is only available after the provider has been set, so the initial binding fails and updates are never processed.What is the new behavior?
Use the new
GlobalProviderState
getter to retrieve the current state of the active GlobalProvider, ornull
if none.This is helpful for binding in XAML, since
GlobalProviderState
is consistently available via the ProviderManager.Instance singleton.PR Checklist
Please check if your PR fulfills the following requirements:
Other information