I just noticed that the stock behavior of the UltraDateTimeEditor is to allow all month/day combinations to UpArrow to day31.
Is there a property that can be set so that the control will be more intelligent? I don't want my users being able to spin to Feb 31st. We are allowing them to spin the year, month and day with the keyboard arrows as per the default settings of the control.
If there is a property that controls this, will it work correctly when SpinWrap is assigned to True?
I've looked through the list and just can't find what I need. I'm also very surprised that this is the default behavior.
Thanks.
The spin button logic validates input on a per section basis; since the largest possible value for any day is 31, it allows up to that value, but does not evaluate the state of adjacent sections when it does this. The reason for this is that to change the value in one section based on the value of another can cause behavior that is disorienting to the user.
Sure, the user might not want the spinner to affect adjacent sections, but I'm sure that he doesn't want to be able to spin to Feb 31st (or Feb 29th in a leap year) either. There's no way that he's going to have warm fuzzy feelings about the application if hew can.
I hope that the section logic for days will be improved to keep the month and year in mind when limiting the spinUp maxValue. I can't imagine any user wanting it otherwise.
The spinDown on Month and Year also need improvement; either affecting the neighboring fields when the mm/yy maxDay has been surpassed, or blocking the change from happening.
Is there a property that governs whether adjacent sections can be spun by changes in the current section? Something like 'SectionSpinSeparate'?
In the meantime, I'm going to have to implement this while Infragistics decides whether to open a change request or not. What is the cleanest way for me to achieve my goals? I will need both functionalities, SectionSpinSeparate true and false.