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.
