DoubleEditBox and Int32EditBox Change Between Builds

Editors for WPF Forum

Posted 10 years ago by Marcus Weaver - Technical Director, Central Precision, Inc
Version: 9.1.0507
I noticed a change in behavior for Int32EditBox and DoubleEditBox between builds 506 and 507. If a minimum value was set in 506, if you typed a value in the box when it was in a grid, the value would revert to the minimum value (for example, if the Minimum property of an Int32EditBox as set to 1 and you typed in a zero, the box would display a 1. In 507, if you do the same thing, the box will show a zero. It seems to work when the control is outside of the grid, but not inside of the grid. Are you able to reproduce this?

Comments (1)

Posted 10 years ago by Actipro Software Support - Cleveland, OH, USA
Hi Marcus,

Yes, we changed the default value of the PartValueCommitTriggers property for the PartEditBox controls when used in a DataGrid. We probably should have marked this as a breaking change (and we've updated the release history as such).

We changed the default based on this post (see item #2). The issue is that the column was being asked to commit it's value back to the data source *before* the Part would lose focus and commit any changes up to the associated PartEditBox. So if you didn't press Enter before moving focus, the display would be wrong.

To fix this we updated the default value of the PartValueCommitTriggers property so that any typing changes would be immediately commited up to the PartEditBox. This would allow the associated column to commit or cancel when needed.

You can get back to the original behavior by setting the PartValueCommitTriggers property to SpinnerChangeOrEnterKeyDown. But the new default fits better with the default DataGrid columns and behaviors.

But, as you pointed out there is another issue with the new default PartValueCommitTriggers. This turned out to be a general bug with the PartValueCommitTriggers.StringValueChange setting, which we have fixed for the next maintenance release.

Actipro Software Support

The latest build of this product (v2019.1 build 0681) was released 8 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.