I'm using RadControls for WinForms (2008.3 1204).
Assume the following: I have a DateTimePicker.
MinDate and
NullDate are both set to 1900/01/01. Now I change the
MinDate property programmatically to 2009/01/01. In this case, the
Value as well as the
NullDate property will also be set to 2009/01/01. Furthermore, even if I set the
NullDate back to 1900/01/01 after this it is not possible to set the DateTimePicker's value to the
NullDate (either by
Value=NullDate or by calling
SetToNullDate() ) - because the value has to be between
MinDate and
MaxDate but the
NullDate is not.
In my eyes this behaviour is senseless. First, the
NullDate property should be completly independent from the
MinDate -
MaxDate range, to set one of them should not effect
NullDate. Second: The DateTimePicker should accept the NullValue date as correct input, even if it is not between
MinDate and
MaxDate.
I think the condition for accepting a value should be
Value == NullDate || |
Value >= MinDate && Value <= MaxDate |
Or am I mistaken?