I'm running into a problem when I try to assign a System.DateTime object to the UltraDateTimeEditor control... Specifically, it's crying about the fact that the system date is 1/1/0001 which apparently is less than the minimum value supported by the control.
My first question is, WHO would create a control that wouldn't accept the Minimum value of a date as defined by the .net system that the control was designed to be used with? To say that that's stupid is putting extremely mildly.
But letting that go for the moment, I assume there must be some clever property setting or something built into the control to handle this issue that, unfortunately, I just can't seem to find. So my question is, what is Infragistics secret on how to handle this issue? And PLEASE, don't tell me I'm supposed to intercept, test, and replace the standard .net system NO DATE (i.e. min date value) with the Infragistics min acceptable date value.
Finally, I absolutely can't believe that ANYBODY would create a Date data type that wouldn't accept 0 (i.e. 00/00/0000) as a valid value. That's just @!#$R%T^& STUPID. Thanx for letting me get that off my chest.
I believe the reason we used the MonthCalendar control was so we did not have to reinvent the wheel. Note that the Infragistics.Win.UltraWinSchedule.UltraCalendarCombo control does not use the MonthCalendar control but rather a native .NET control that realizes most of the same functionality. Note, however, that this control does not support masking as does the UltraDateTimeEditor.
Brian Fallon said: One answer to this question is Microsoft, Inc., who designed the MonthCalendar control that is used in the dropdown portion of the UltraDateTimeEditor.
One answer to this question is Microsoft, Inc., who designed the MonthCalendar control that is used in the dropdown portion of the UltraDateTimeEditor.
I would suggest that Infragistics would be FAR (extremely far) better off NOT utilizing Microsoft controls, such as the afore mentioned MonthCalendar control, because of exactly these sorts of ignorant, pain in the butt type problems.
Brian Fallon said: This too is attributable to a design decision made by Microsoft.
This too is attributable to a design decision made by Microsoft.
Again, so why does Infragistics utilize and \or emulate Microsofts stupidly designed controls? This just perpetuates the problem.
Wolven said:My first question is, WHO would create a control that wouldn't accept the Minimum value of a date as defined by the .net system that the control was designed to be used with? To say that that's stupid is putting extremely mildly.
Wolven said:So my question is, what is Infragistics secret on how to handle this issue?
Wolven said:Finally, I absolutely can't believe that ANYBODY would create a Date data type that wouldn't accept 0 (i.e. 00/00/0000) as a valid value. That's just @!#$R%T^& STUPID. Thanx for letting me get that off my chest.