Hello
Since upgrading to v18.1.6 the time portion of the MaxDate value for an ASPxDateEdit is not being set. In the attached video you can see that in v17.1.7 (our previous production version) the MaxDate time is being set correctly. In v18.1.6 (our current production version) the time is being set to 12:00AM.
Regards
James
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hello James,
Let me explain the cause of this modification. The MaxDate property should define only the maximum day that can be selected in the editor and shouldn't take into account certain time of this date. Therefore, the behavior of this property was modified so that the time part of the date, which is used for date comparison, is always set to the certain time of this day.
We have discussed this behavior and came to the conclusion that changing the time value to "23:59:59" which is the last second of the maximum date would be more appropriate in this scenario. Would you please clarify if the situation when the time part of the MaxDate value is set to "23:59:59" is more suitable for your case or you need to preserve the initially defined time and use it while performing MaxDate validation and comparing dates? If so, please describe your certain scenario, which requires such behavior and your requirements in greater detail.
What I would like is for it to work exactly as it did.
In my scenario the user is recording an Event. The field in question records when the Event occurred. In the previous version the field max date was set to the current date and time so the user could not enter a future date but they could change the time to earlier in the same day (a very common action). In the new version they cannot record the actual time the Event occurred if it was on the same day.
How can this be resolved?
Also I would like to know why it was changed. I searched the change log from v71.2.9 to v18.1.6 and can find no reference to this change. Where is the information about the change?
Thank you for clarifying your scenario, James.
We have decided to revert to the previous behavior so that MinDate/MaxDate take the time part into account. Please accept our apologies for this inconvenience.
I've forwarded this ticket to our developers. We will inform you about our progress.
Thanks for that.