Closed GoogleCodeExporter closed 9 years ago
This issue was updated by revision dda4f60bff00.
Implementation and tests done. Clean-up, especially related to old code, and UG
documentation missing.
All these are now valid formats:
00:00:01
0:00:01
100:00:00
00:00:01.5
00:00:01.123
00:01
00:01.5
Also all these work although they are a bit questionable:
0:0:1
00:99
100:100
Original comment by pekka.klarck
on 4 Jun 2014 at 5:48
This issue was updated by revision bd1a27b2e298.
Documented the new format in User Guide. Changed terminology from "clock" to
"timer". That needs to be done in code too.
Original comment by pekka.klarck
on 4 Jun 2014 at 5:48
This issue was updated by revision cda8e2a10a19.
Refactored code and utests.
- Use 'timer' instead of 'clock' terminology.
- Some general cleanup.
Original comment by pekka.klarck
on 4 Jun 2014 at 5:48
Original comment by pekka.klarck
on 4 Jun 2014 at 5:49
This issue was updated by revision e1de3ab2ce0f.
Other tests revealed that earlier time format supported also
'millisec(s)' and 'msec(s)'. That was probably an accident caused by
how the time format was parsed, but better to keep supporting them
anyway. Also enhanced related tests otherwise.
Original comment by pekka.klarck
on 5 Jun 2014 at 8:56
This issue was updated by revision ddea13b48914.
DateTime supported also + prefix with timer strings. Now timestr_to_secs
supports it too.
Original comment by pekka.klarck
on 5 Jun 2014 at 8:56
Original issue reported on code.google.com by
janne.piironen@gmail.com
on 22 May 2014 at 8:17