I have an UltraDeteTimeEditor with MinDate = 01/01/2000 12:30 AM, MaxDate = 01/01/2000 11:59 PM and Value = 1/1/2000 12:31:00 AM. The spin button is set to visible. I'm attaching a test project with that configuration.
Try the following tests:
1) Run the app, select the minutes an click the down spin button. The control allows me to set the time to a value lower than 12:30 AM. I think that's a bug. The minimum should be 12:30 AM. When the control contains that value the down spin button should be disabled.
2) Stop the app, set the SpininCrement to 1 minute. Run the app, select minutes and click the down spin button. The value changes from 12:31 AM to 1:00 AM and the down spin button is disabled. That's not the expected behavior. I expect the same results described on test #1.
I'm I missing something?
Thanks,
Oscar.
Hello,
I have sent your product idea directly to our product management team. Our product team chooses new product ideas for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this product idea is PI12060062.
Thank you for your request.
Thanks for the answer Brian.
I understand your point. It looks like Min/Max validation is not properly implemented for the time portion of the DateTime. I'll submit a feature request.
Now, regarding the NumberSections... Is there a way to knwo which section is being edited? for example, if the user clicks the MinuteSection how can I determine the caret position is on top of that section?
I believe the time component of those properties is not applicable, i.e., the property names are MinDate/MaxDate as opposed to MinDateTime/MaxDateTime. If you like you can submit a feature request for a way to restrict the time range as well.
The Infragistics.Win.UltraWinMaskedEdit.NumberSection class exposes MinValue and MaxValue properties. A "section" is typically the part of a mask that lies between the literals, for example an HourSection or MinuteSection. These are settable properties, so you can impose a minimum/maximum on a per-section basis. The DateTimeEditor exposes a Sections collection (by virtue or deriving from EditorWithMask), so you can access them from that collection. I suppose in your case you would do something like case each one to the desired type (HourSection, MinuteSection, etc.) and if the cast is non-null, set the MinValue/MaxValue accordingly.