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.
Updates to binding sources can now be delayed by configuring each binding.
What is the updated/expected behavior with this PR?
The delay feature works in the same way as WPF's. When the target property is changed, a
DispatcherTimer
is started (or restarted) and the source is only updated when the timer elapses.As with WPF, there is no delay when the source is updated via
UpdateSourceTrigger.LostFocus
orBindingExpressionBase.UpdateSource()
. Nor is there a delay whenBindingMode.OneWayToSource
is active and a new source object is provided.Other binding types
MultiBinding
does not support writing back to the source, so does not have aDelay
property.TemplateBinding
could supportDelay
but I didn't implement it there. WPF's equivalent type doesn't have it, and I also don't see a use case within the context of aControlTemplate
.Breaking changes
None
Obsoletions / Deprecations
None
Fixed issues
Fixes #7380