DoubleEditBox: PropertyChanged doesn't work

Editors for WPF Forum

Posted 12 years ago by Bernhard Wahl
Version: 9.2.0513
Platform: .NET 3.5
Environment: Windows Vista (32-bit)
<Editors:DoubleEditBox x:Name="AmountTextBox"
Value="{Binding Path=Amount, Source={StaticResource subsetWindowViewModel}, UpdateSourceTrigger=PropertyChanged}">

The editbox has a binding which should get fired after "PropertyChanged". Now i checked out that i always get a "PropertyChanged" with an old value and after i leave the textbox ("LostFocus") i get the current value set to the Amount property.

I'm working with the newest version (downloaded it today)

Please fix this bug !!!

Comments (3)

Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA
Hi Bernhard,

By default, changes made by typing are not immediatlely committed from the part up to the parent PartEditBox. The changes are commited when the part loses focus or the user presses Enter. This behavior can be altered using the PartValueCommitTriggers property.

Sounds like you will want to set it to "All", which includes the StringValueChange (which encompasses typing).

Actipro Software Support

Posted 8 months ago by Procam


after 11 years this post was created. Is there a solution for the DoubleEditBox to work as TextBox, it means the binding to be raised when setting UpdateSourceTrigger=PropertyChanged ? The reason I use this control is the nice functionality of autocheck for Minimum and Maximum value. I wanted to try the "PartValueCommitTriggers" but where?

Thanks for the answer.

Posted 8 months ago by Actipro Software Support - Cleveland, OH, USA


The Editors API was updated in the 2017.1 version when edit boxes were refactored.  In the new API, the editBox.CommitTriggers property can be set to any PartEditBoxCommitTriggers value.  There are All or StringValueChange options in that enum.  The "Edit Box Basics" documentation topic mentions the CommitTriggers property and it affects behavior when values change.

Actipro Software Support

The latest build of this product (v21.1.3) was released 17 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.