time - Proper way to round a second-precision count-down display -


i need display time span user, in m:ss format, indicates how far in future event happpens (e.g. download finished).

now assume, event 1,3s in future. should display 0:01 or 0:02?

  • the former (rounding down) seems more natural in consistent hypothetical, more precise 0:01.500 display.

  • the latter avoids awkward situation display show 0:00 1 second, until event occurs.

is there standard on matter offers guidance?

if count down, should display ceiling.

1,7 -> 2 1,2 -> 2 1,0 -> 1 0,1 -> 1 0,0 -> 0 

this way 'instant end' (no 0:00 1 second) , proper perceived remaining time: when user/player see 0:01, knows has 1 second left.


Comments

Popular posts from this blog

searchKeyword not working in AngularJS filter -

sequelize.js - Sequelize: sort by enum cases -

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -