Issue 105344 - Input of time data into the MM:SS.00 format
Summary: Input of time data into the MM:SS.00 format
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: formatting (show other issues)
Version: 4.1.0-dev
Hardware: PC Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-25 01:44 UTC by snofriacus
Modified: 2013-11-07 10:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description snofriacus 2009-09-25 01:44:19 UTC
I'm working with a spreadsheet which uses the MM:SS.00 time format to do
calculations on running and swimming times. I enter that it took me 17 minutes
and 9 seconds (17:09.0) to run 2 miles, and the spreadsheet then calculates that
this was a pace of 08:34.50 per mile, and 02:08.63 per quarter mile. This all
works fine, as long as I enter the number as either 17:09.0 or 0:17:09 Entering
0:17:09.0 works fine too, as might be expected. 

But all three of these data entry formats involve the typing of extra zeros. The
format I'd prefer to be able to type is simply 17:09. But when I do this, Calc
makes some bad assumptions about which parts of the number to assign to minutes,
seconds, etc. It decides that "09" must be the number of minutes, and just
throws out the "17" since there isn't a place for hours in the MM:SS.00 format.

It seems like it should be easy to have the input function correctly deduce from
just the input "17:09" that "17" is minutes and "09" is seconds, since there are
no hours in the MM:SS.00 format.

I find this same behavior both when typing data and when cutting and pasting
data from a text file.
Comment 1 Edwin Sharp 2013-11-07 10:33:10 UTC
17:09 gives 09:00.00
AOO410m1(Build:9750)  -  Rev. 1536093
Rev.1536093
Win 7