View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006263||JEDI VCL||00 JVCL Components||public||2014-03-05 16:53||2019-08-22 13:26|
|Target Version||Fixed in Version|
|Summary||0006263: No On change event call for DateTimePicker|
|Description||I added an function for the OnChange Event. This function never gets called when you type in the control and change the item. It works with the standard TDateTimePicker.|
This would also be a great time to fix the known issues with the default TDateTimePicker where "What you see isn't what you get" if you have both the date and time displayed and you change values not all values get updated on the back side, only values associated with "Kind" property get updated.
Kind = dtkDate
Format = 'MM/dd/yyyy hh:mm tt'
//modify the hour, then read the time in code and it isn't modified.
This can be fixed in the OnChange Event by updating the date/time value using the text property of the component.
At the very least, expose the .text property of the component so the user can do this manually.
|Tags||No tags attached.|
||Please provide the zipped sources of a sample application showing this|
JVCL_6263.zip (54,052 bytes)
I created a demo project now. It shows two things:
1. the OnChange event is fired just fine in the current version
2. the thing with not changing the entered time internally when Kind is dtkDate is indeed the case, but I rather think this is as designed. or what would the Kind property be for otherwise? If Kind is dtkTime the entered time is really changed.
What about this one:
The thing with not changing the entered time internally when Kind is dtkDate is indeed the case, but I rather think this is as designed
or what would the Kind property be for otherwise? If Kind is dtkTime the entered time is really changed.
Is it as designed? if yes, the whole issue might be marked as resolved as the OnChange event as per my demo does fire.
If it is not designed we'd need to change it accordingly but I don't know how the decision of the design is in this case.