I've changed the behaviour of timeParse a little. Now if it doesn't find a separator and the timeVal string contains at least 4 characters (and the timepicker is not configured for minutes or hours only) it simply uses the first 2 characters for the hours and the second 2 for the minutes. Also added a configuration option that can turn this behaviour off.
The main reason I did this is because I've come to expect this kind of behaviour (a time entering field interpreting, for example, "1345" as "13:45").
Hi there
I've changed the behaviour of timeParse a little. Now if it doesn't find a separator and the timeVal string contains at least 4 characters (and the timepicker is not configured for minutes or hours only) it simply uses the first 2 characters for the hours and the second 2 for the minutes. Also added a configuration option that can turn this behaviour off.
The main reason I did this is because I've come to expect this kind of behaviour (a time entering field interpreting, for example, "1345" as "13:45").
Cheers,
Wieke