Why doesn't the NewValue in the event arguments hold the value in the editor? Isn't it a bit convoluted to have to access the editor for the value?
Thanks for the update. Using e.Cell.Value is fine, but I think it would also be good to clarify on the documentation.
Hello,
Thank you for your patience.
I have discussed your concerns with our development teams and for some columns (like TemplateColumn and UnboundColumn) the new value cannot be predetermined because of the use of DataTemplates and user-defined bindings. In our future releases of the product the ‘ExitEditingCellEventArgs.NewValue’ will be null for such cases to avoid confusion.
You can still access the new value through e.Cell.Value if required.
I have logged this behavior with our developers in our tracking system, with an issue ID of 115888. I have also created a support ticket on your behalf with number CAS-94963-MBXT7S in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.
Hello Michael,
Thank you for the provided application. I will contact the development department regarding more information about your issue.
Click the items source button, then enter a value into column C. The messagebox shows the NewValue object.