Thx for picking this up.

This means pretending to be more accurate while being less accurate, while increasing code complexity.

If you launch at 10:02:00 and land at 10:07:59, how long was your flight?

• accurate value is 5m59s
• accurate truncated value would be 5 minutes
• accurate rounded value would be 6 minutes
• currently, XCSoar displays 5 minutes (= accurate truncated)
• after TimesStatusPanel: Cut seconds of for the final flight time calculation. #1027 XCSoar would display 5 minutes

If you launch at 10:02:59 and land at 10:08:00, how long was your flight?

• accurate value is 5m1s
• accurate truncated value would be 5 minutes
• accurate rounded value would be 5 minutes
• currently, XCSoar displays 5 minutes (= accurate truncated)
• after TimesStatusPanel: Cut seconds of for the final flight time calculation. #1027 XCSoar would display 6 minutes (= ???; so wrong, no matter how you look at it)

(Note: currently, XCSoar truncates both the start/landing time and the flight duration; no rounding. It can be debated whether truncation or rounding would be better, and if somebody feels XCSoar should round displayed values, I'd agree to change that.)

#1027 adds a second layer of truncation to calculate the flight duration, it truncates twice, losing more precision. This makes it less accurate than the current behavior, which truncates only once.

I think this whole thing is a non-issue that does not need to be addressed at all. This is just an artifact of displaying less precision on the UI than XCSoar has internally. Attempts to "solve" this non-issue with #1027 only lead to complicated code, bloat, reduced performance and fragile code.

Ok, Max, I guess you did not understand the issue I described first hand. I do not care about rounding or truncating, not at all. I just like to see a consistency on the GUI that shown flight time equals landing time - launch time. And that is not given.

Picking up your second example .. nomatter what the flight time is more or less wrong. But the GUI will try to make you believe that the flight went from 10:02 to 10:08 and took 5 minutes.
I just would like to see a match here that I can take over in my flight book. Currently it is a 50:50 chance of having an inconsistency then.
But good that we figured that the code change is not the issue, it is the issue itself. Here we are. Still a lot of taste and prospectives to align anyways.

Hey lordfolken, what to do here? You put this issue on the to do list, but after this exchange of thoughts it is unclear to me how to procede.
Do we want to see a consistent GUI where start time and flight time adds up to a landing time, or do we not care about this inconsistency, prefering an "accuracy" on rounded time stamps, that leads to a not consistent flight time here.