[In 11.2.5] Time fields: Allow period instead of colon

[StasUshomirsky]

Mike,

I would like to propose an enhancement to the behaviour of all time entry fields:
Allow the decimal period (on the numeric keypad) to be used instead of the colon as a separator between minutes and seconds.

This would DRAMATICALLY speed up data entry! Typing the colon is cumbersome, since it requires holding SHIFT, takes two hands, and forces the user to switch from the numeric keypad to the main keyboard area. If we only used the numeric keypad, then typing time values would be much faster!

.8 ==> interpret as 0:00:800 (this already works)
25 ==> interpret as 0:25.00 (this already works)
1.41 ==> interpret as 0:01.410 (this already works)
2.1.7 ==> interpret as 2:01.700 (this is the proposed new behavior)

I would love to see ALL time fields accept the period instead of the colon.

The period is only used for data entry -- once the field loses focus, the period get replaced with a colon and proper time formatting is displayed.

Thank you!

[Mike Daniell]

Included in 11.2.5 RC3. All time fields are validated and reformatted where necessary using a common procedure, so I have modified this procedure to optionally accept "." instead of ":". For example, 1:23.456 and 1.23.456 will both be accepted as 1 minute, 23.456 seconds.

[StasUshomirsky]

Wonderful! Thanks so much Mike!