Deadline should be written hh:mm:ss OR mm:ss OR mm.fraction_of_m NOT mm:s

[GoogleCodeExporter]

Deadline should be written hh:mm:ss OR  mm:ss OR mm.fraction_of_m NOT mm:s

To a new user, it is hard to recognize the deadline as a time.

Original issue reported on code.google.com by Tro...@gmail.com on 7 Nov 2010 at 6:50

[GoogleCodeExporter]

Original comment by azzur...@gmail.com on 8 Nov 2010 at 10:21

• Added labels: Component-UI, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

agreed, should always show the ones digit, even if its a multiple of 10.

also when loading from history it would be nice if it didnt convert it into 
pure seconds format and left it in the mm:ss format that you're used to seeing 
in replays / game time. Any time I load from the history it switches (for 
example) 6:00 to 360 and I have to go back through and rewrite the 360 as 6:00 
or else it doesnt mesh with the game-timer in my head.

Original comment by EKlip...@gmail.com on 8 Nov 2010 at 11:07

[GoogleCodeExporter]

Yeah, I think that it's confusing to see the deadline written in seconds when 
loaded from the History.

Original comment by mike.angstadt on 23 Nov 2010 at 1:40

[GoogleCodeExporter]

Original comment by mike.angstadt on 24 Nov 2010 at 2:36

[GoogleCodeExporter]

Fixed in r188

Original comment by nafets...@gmail.com on 5 Dec 2010 at 5:03

• Changed state: Fixed

[GoogleCodeExporter]

This issue was referring to the Deadline field. :) When a simulation is loaded 
from History, the Deadline field for each waypoint displays the total seconds 
instead of m:s.  For example, a waypoint with a Deadline of 3 minutes 30 
seconds would be displayed as "210" instead of "3:30".

Original comment by mike.angstadt on 5 Dec 2010 at 1:43

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in r233.

Original comment by mike.angstadt on 10 Dec 2010 at 11:35

• Changed state: Fixed