I have a number of Date/Time editors that default the time component to 23:59. A user has just reported that he can change the date within the 'current month' and the 23:59 remains however, if he changes to a date in another month, the time component is set to 00:00.
I have confirmed this is the case in our development system also. Is there a work around for this issue.
Our environment is:
Display Format: DateTime "G"
Edit Format: DateTime "G"
Edit Mask: G
Null Date: 01/01/1800 12:00:00 AM
Null Text: / /
This initial value for the control is set using:
Me.ToDate.DateTime = Date.Today.Add(TimeSpan.FromMinutes(1439))
TIA - Peter
Steps to Reproduce:
Run the attached project (Q243059c.zip).
Open the DateEdit popup.
Move to another month, and click some date.
The Time part of the date is set to 00:00
Don't change the Time part, as in other date selecting scenarios.
Your sample exhibits the same problem I reported.
Did you change your regional settings to Australia? That being said I changed mine to US and it didn't make any difference.
My development system is Vista and our production system in Server 2008 (Std Ed) - both with latest service packs.
I've set the current culture to Australia ("en-AU"), but still can't reproduce this issue. As far as I see, you are using a rather old version of our components. We recommend that you upgrade to version 9.2.10. If this doesn't help, please provide detailed steps on how to reproduce this issue, or record a video demonstrating it.
Thanks for the avi - yes, I can see the sample works fine at your end. However the solution you sent for me to have a look at doesn't contain any code for the SimpleButton1 click event.
Also I note:
1) This version had Dx 9.2 references while the previous version you sent had 9.3 references. I changed the reference in this sample to 9.3 because you advised me to move to 9.3.
2) Both this solution and the previous had to be 'converted' by Visual Studion because it advised they had been created in previous version of VS and a conversion was needed. Could this be an issue?
Previously my only testing had been with changing the date via the calendar drop down (normal usage for us) and never via just using the keyboard.
a) When using the keyboard it works fine.
b) When using the calendar drop down and selecting a day in another month that is visible, e.g. selecting 30 Dec in the January 2010 calender it works fine.
c) When using the left / right arrow in the calender control to move to another month and selecting another date then the time is set to 00:00.
If you can please send me the exact solution used in the avi I will try to find the difference in our environments that cause the problem.
The project I attached to my previous message is the one I used to create a video. I've also tested this scenario with both DXperience versions 9.2.10 and 9.3.2 (I converted the project using the ProjectConverter tool), and in both VS2005 and VS2008 IDEs. The result is the same. Possibly, there are some other customized culture settings on your machine, which cause this issue.
Yes, I attached a project that uses version 9.2.10. You should use the ProjectConverter tool to convert it to another version. I already did this and tested version 9.3.2 as well (attached is a converted project for your reference). Yes, the button's Click event isn't handled. I use this button only to move focus from the DateEdit.
I'm looking forward to hearing from you.
Well, a partial answer. If I set the property: VistaDisplayMode to False then I get a calendar dropdown in the same format as your avi and the time is not set to 00:00.
Changing this property in all out forms and distributing the update is a bit cumbersome plus we prefer the format and features of the existing calender dropdown down. Any suggestions for a work around?
Thank you very much for the additional information. It seems the this issue doesn't depend on the current culture. I've reproduced it by setting the DateEdit.Properties.VistaDisplayMode property to True. It appears to be a bug in our control. We'll research this problem further and try to resolve it as soon as possible.