You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the GUI displays a duration, e.g. the run-time of a script on the active scripts tab, or the time since installing augs on the stats tab, it formats it with numeric values and written unit names, e.g. "6 hours 3 minutes 2 seconds".
Currently, any time element which is 0 is omitted entirely, e.g. "6 hours 12 seconds" instead of "6 hours 0 minutes 12 seconds". However, it makes such times less readable - it is easy to mistake "6 hours 12 seconds" for "6 hours 12 minutes" at a glance, because we expect the unit after 'hour' to be 'minute'. Similarly, if you have multiple dates with the same number of displayed components but different units, its easy to miss that difference in units, e.g. if you have "6 hours 12 minutes" followed by "6 minutes 40 seconds", it's easy to mistake that as two very similar times rather than two times which differ by an order of magnitude.
I propose that this be changed, so that only leading components are omitted when 0.
When the GUI displays a duration, e.g. the run-time of a script on the active scripts tab, or the time since installing augs on the stats tab, it formats it with numeric values and written unit names, e.g. "6 hours 3 minutes 2 seconds".
Currently, any time element which is 0 is omitted entirely, e.g. "6 hours 12 seconds" instead of "6 hours 0 minutes 12 seconds". However, it makes such times less readable - it is easy to mistake "6 hours 12 seconds" for "6 hours 12 minutes" at a glance, because we expect the unit after 'hour' to be 'minute'. Similarly, if you have multiple dates with the same number of displayed components but different units, its easy to miss that difference in units, e.g. if you have "6 hours 12 minutes" followed by "6 minutes 40 seconds", it's easy to mistake that as two very similar times rather than two times which differ by an order of magnitude.
I propose that this be changed, so that only leading components are omitted when 0.
Version: a3c599e
The text was updated successfully, but these errors were encountered: