-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Porting WPF UpdateSourceTrigger #3754
Comments
The missing UpdateSourceTrigger is a headache in some scenarios:
|
This part is expected to be managed on lower layer and not by View. With ReactiveUI it's quite simple using Throttle mechanism. It's always possible with some other third-parties.
Agree, in some cases for binging between elements we care only about final value after lostfocus, so UpdateSourceTrigger will be really helpful in this case. |
Yes, throttling can help but it is not semantically the same, also for client->server updates it makes sense the whole data is sent as soon as the field gets a input confirmation from the user, which is often modeled as a LostFocus event. |
Hello, Is this feature in your roadmap? is there a chance to see it in the next release? |
For now you can use behaviors for a workaround. <TextBox>
<Interaction.Behaviors>
<example:LostFocusUpdateBindingBehavior Text="{Binding Text}"/>
</Interaction.Behaviors>
</TextBox> It's a bit more verbose, but should solve your issue. |
Made a PR for this: #7797 |
Hi @Avaloniateam, is there any chance that the feature will be implemented? It's very annoying to add behaviors. |
There is a plan to look at the binding system but right now we're focused on shipping v11. |
thanks and add this to milestone V11 |
Having something like the WPF
Binding.UpdateSourceTrigger
(https://docs.microsoft.com/en-us/dotnet/api/system.windows.data.binding.updatesourcetrigger?view=netframework-4.8) in Avalonia would be helpful.The text was updated successfully, but these errors were encountered: