Introduce BindingProxy to mitigate temporary XAML binding failures#4045
Open
nicolaihenriksen wants to merge 1 commit intomasterfrom
Open
Introduce BindingProxy to mitigate temporary XAML binding failures#4045nicolaihenriksen wants to merge 1 commit intomasterfrom
nicolaihenriksen wants to merge 1 commit intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #3814
Introduces a
BindingProxyto mitigate the temporary binding failures occurring when bindings are used to reference something not in the current visual tree.The issue was easily reproducible. I also went through the pages of the demo app (just opening them) to spot any immediate XAML binding failures. There were 2 apart from the
ProgressBar:BindingProxy)