Declined
Last Updated: 21 Jun 2018 14:52 by ADMIN
Robert
Created on: 09 Apr 2018 09:45
Category: UI for WPF
Type: Bug Report
1
DateTimePicker: text-to-date parsing does not accept uppercase 'A' for typed month entries
Affects RadDateTimePicker control of TelerikWPFControls version 2015.1.1

When the user is typing in a specific date and time, the RadDateTimePicker control's text-to-date parsing doesn't accept an uppercase 'A' at the start of what it expects to be the month's name and automatically errors (displays a tooltip showing 'Error') as soon as an 'A' is input. This prevents the user from entering dates and times more specific than the clickable selection for the months of 'April' and 'August'. However, replacing the 'A' with a lowercase 'a' allows the user to proceed with entering more specific dates and times as normal without the 'Error' tooltip showing. 

E.g.: 
1) the user selects 03 April 2018 17:00:00 from the control's clickable selection of date and times;

2) they then try to type more specific minutes and seconds, e.g. 03 April 2018 17:45:23, but this is not accepted by the control and it displays the 'Error' tooltip;

3) workaround - the user changes 'A' of 'April' to a lowercase 'a', as in 'april'. Now the 'Error' tooltip goes away and the user is able to enter and save the more specific date time of 03 april 2018 17:45:23.

This bug only came to light once the control was live in production (released in January) and prevented our users from entering the specific trade date times necessary for regulatory purposes.

Can you tell me if this bug has been fixed in later versions of the control?

Thanks and regards,

Robert Fiteni
2 comments
ADMIN
Kalin
Posted on: 28 May 2018 07:14
Hi Robert,

If you experience the issue with the latest release as well - please open up a support ticket.

Regards,
Kalin
ADMIN
Kalin
Posted on: 20 Apr 2018 11:23
Hi Robert,
 
We have fixed some issue with the time part parsing since 2015, so this should be resolved. If you are able to attach a sample project demonstrating the issue - we can test it with the latest release and investigate if it is still present. Also please let us know what is the exact Culture of machine where the application is used.

Regards,
Kalin
Telerik