Time Format Vote

[Jyers]

Regarding #111, I wanted to take a vote to see what the community thought. React to this post to cast your vote.

00h00m Format: 👀

00:00 Format: 🚀

[Henri-J-Norden]

The claim of 00h00m being "more universal and human readable" is not based on fact. 00:00 is the international standard representation for time as specified by ISO 8601 and is perfectly human readable.

[tiagofreire-pt]

The claim of 00h00m being "more universal and human readable" is not based on fact. 00:00 is the international standard representation for time as specified by ISO 8601 and is perfectly human readable.

The proposed format for duration (HH h mm m) is also a valid standard and defined in the ISO 8601 itself: https://en.wikipedia.org/wiki/ISO_8601#Durations

[Henri-J-Norden]

Oh interesting, I actually did not know that, as I don't think I've ever seen it used.

[tiagofreire-pt]

Hi,

Yes, the time representation is standardized as HH : mm, with ISO 8601.

What I'm proposing here is not a representation of time itself, as an instant moment of time, but duration or accumulated amount/elapsed/remaining.

The proposed format for duration (HH h mm m) is also a valid standard and defined in the ISO 8601 itself: https://en.wikipedia.org/wiki/ISO_8601#Durations

Even further, is the format chosen by the 2 most predominant slicers to represent printing duration:

Cura:

Prusa Slicer:

Proposal:

I hope that we could all agree on this. :)

Thanks.

[Cal-LF]

I can function with either style.

[amandamana]

00h00m appears less readable to me because the 'h' and 'm' characters are much wider on the screen than a colon, which makes it more difficult to visually chunk the numbers. The low resolution and narrow viewing angle of the V2 screen don't help. I also think that shorter strings are easier to read, and that either 'h' or 'm' is redundant in view of the other.

Also note that for the proposed duration to comply with ISO 8601, it needs period and time designators, such as PT00H00M.

I don't think the issue is human readability, but possible ambiguity about whether 00:00 is hh:mm or mm:ss. Of course, that's easy to figure out when looking at a live display.

When possible, I'd like to see h:mm:ss (no leading zero for h) as the most informative, unambiguous format.

[Legsmaniac]

@tiagofreire-pt Here's another one for you.

Have just finished a nearly 8 hour print.
Using the latest Jyers flavour, I'd forgotten I'd set my config to tell me total finished print time.
Here's what I see..........

So there's another example of time format, the format which is being proposed.
I say yes, I'd happily go with it. 😉

[amandamana]

I think that's an example of how space characters are added because 7h43m37s runs together with poor readability on the display. That solution helps, but it's not always possible when screen space is at a premium. And even with the spaces, I think 7: would be easier to read off angle than 7h.

[Henri-J-Norden]

It would be possible to support both formats, by simply adding a "Time format" toggle in one of the menus. I have been working on a leveling menu for UBL with a mesh viewer, so extending the menu is pretty straightforward. I have not, however, looked into how to add a new EEPROM variable, which would be necessary in this case.

[Jyers]

This was actually what I was planning on doing considering the situation. I was also a little turned off by the eeprom aspect, but if have time soon I'm sure it would not be the worst thing to figure out.

[Jyers]

At some point I will hopefully implement both of these formats and provide a setting in advanced options to choose. That is when I figure out how to read and write to eeprom...