Thanks, I appreciate your reply.
I pulled down the latest code base (2.1.0.0), added the code snippet you suggested and tried that, but it still seems to be acting weird.
It still seems to be doing the same thing. Once losing focus, instead of resetting to the original date (from the invalid date) it resets to the first digit of the invalid date. For example, setting the day with the cursor and keyboard to 78 and after losing focus, the date changes to 07. I would expect it to behave like the .NET DatePicker, and I think you said that is to be implemented in a future release.
I pulled down the latest code base (2.1.0.0), added the code snippet you suggested and tried that, but it still seems to be acting weird.
It still seems to be doing the same thing. Once losing focus, instead of resetting to the original date (from the invalid date) it resets to the first digit of the invalid date. For example, setting the day with the cursor and keyboard to 78 and after losing focus, the date changes to 07. I would expect it to behave like the .NET DatePicker, and I think you said that is to be implemented in a future release.