Here's a simple example of a problem we have throughout a rather large app:
We've got a view with a RadRibbonButton for 'Save' and a RadDatePicker. When the user clicks Save, the view remains open after saving. The problem we have is that users are clicking on Save while in the process of editing the date in the TextBox of the RadDatePicker. The result of this is that the 'old' date value is the one that's actually saved in the button click event, THEN the DatePicker updates to show the 'new' date value. (In our real app, this gets very confusing with various validation, etc.)
So, we want to make sure that what is saved matches what is displayed after the save. Do you have any suggestions for how to either 1) Force the RadDatePicker to process all input before saving in the ButtonClick, or 2) Prevent / abort any pending inputs to the DatePicker in ButtonClick.
(We'd prefer to find a solution we can package in our custom class derived from DatePicker, which is used in many places throughout the app, if possible.)