[ADDED] build time in minutes.. or hour correctly.

[AndersE]

sure minutes is ok like 90min but converting that to 1.50 hour is just stupid (we don't count 100 on an hour.) .. i want it to say 1.30 and no h after that.

[lkeppner]

I would tend to disagree with this request as written. Hours is a legitimate measure and seeing 534 minutes does not really help me easily figure out what time the job will be done. If it says 8.9 hours then I can easily estimate how long the job will take. I could, however, support seeing an hh:mm format. So, instead of 534 minutes it would show 01:54... In fact, if you are printing over USB, the system could go one step further by adding the job time to the system time once you hit print and just tell you what time the job may be complete!!

Perhaps this is what you meant??

[AndersE]

I don't know if you got me right. I still want the minutes AND hours, minutes.
But of your example : now does 1.54 mean 1 h and 30 min something. Not 1 h and 54 minutes. They are counting 100 parts
in an hour and that is CONFUSING.

If i read 2.50 i read it as 2 hours and 50 minutes, not 2 h and 30 min.

[AndersE]

Forgot to write that this is the build statistics screen where you also se the material cost etc.
Not the printing dialog.
I always look at this first before starting a print.

[lkeppner]

I think it is all in the period versus the colon.

1.54 means 1 hour and 54/100 of an hour (or 32 minutes) while 1:54 would mean 1 hour and 54 minutes. This would be the conventional notation...

[jimc]

I think i agree with keppner. Until anders posted something i never even took note of it. If i see 1.50 hrs that to me is an hour and a half. Never would i think an hour and 50 min. I guess everyone is different but i have never been confused by the time it gave. Not that it matters anyway simce its never correct.

The feature request should be in the prefrences somewhere a % offset for the time estimates. If it tells me its going to take an hour and it consistantly takes 1.5 hours then we should be able to put a +50% in there somewhere to tune the timer to our printer

[AndersE]

well i don't know anyone who reads 1/100 of a minute, no matter . or : . Is that some engineering way of thinking or is it some US thinking like in inches vs cm, miles/h or km/h?
Because i can not think inches and feet without a calculator for example.

Any random person would not think or see the difference between a . or : in a timedisplay i think.

[KeyboardWarrior]

well i don't know anyone who reads 1/100 of a minute, no matter . or : . Is that some engineering way of thinking or is it some US thinking like in inches vs cm, miles/h or km/h?
Because i can not think inches and feet without a calculator for example.

Any random person would not think or see the difference between a . or : in a timedisplay i think.

I think this is the answer

[laird]

sure minutes is ok like 90min but converting that to 1.50 hour is just stupid (we don't count 100 on an hour.) .. i want it to say 1.30 and no h after that.

In the US, and most countries, there's no ambiguity: 1.50 hours means one and a half hours, because 1.5 means one and a half, and 1:50 hours means one hour 50 minutes, because colon is the separator between hours and minutes.

The place where it's ambiguous is in Germany (for example) where they use . as the separator between hours and minutes. So in Germany 1.50 hours could be read either as one and a half hours, or as one hour 50 minutes. Though Germany recently (20 years or so) formally switched to using the colon for consistency with everywhere else, many people still write it with a period.

What most software tries to do is use "human friendly" small-ish numbers, and switch the units around. So, for example, a timer would count down by hours with one decimal point (e.g. 7 hours, 2.5 hours, 2.2 hours, etc.), until it gets to two hours, then switch to minutes, because, as you say, 90 minutes looks more friendly than 1.5 hours. Other timers use HH:MM:SS, which is simpler, and consistent, but less friendly.

[S3D-Jason]

This was updated in version 2.0. The software now says the build will take "XX hours XX minutes" to avoid any confusion.