Just a comment really, when using a rad datetime picker, it might be useful to be able to catch some event based on the date that a user has selected.
The problem is that with the select/unselect behaviour of the calendar in the datepicker, there is an inbetween event "valuechanged" fired, with the date at that point being "1 January 1980", or datemin, so you can't really attach anything directly to that event without fudging it...
Now I understand the select/unselect of a calendar is why this behaviour exists, but realistically, when using a datepicker control, WHY would anyone want that inbetween date? Surely we're only ever interested in the date that the user has selected? This feels to me like seeing unecessarily the mechanics of the control?
Would it not be possible to segregate the events into a "real" ValueChanged event which would only fire once the
transaction (if you like) of changing to mindate and then to the actual date clicked on had completed and then relegate the current ValueChanged to something more accurate like "CalendarSelectionChanged"?
I think that a datepicker control should allow me to capture what the user has actually selected without having to filter out spurious events.
Incidentally, how DOES one filter out that spurious event when the date selected happens to be the minimum date? Does your control fire valuechanged twice, both times with the same (mindate) value in the Value property?