Why Could Total Time Differ Between Mac and iPhone?

NOTE: This issue was resolved in version 3.0.4 for the iPhone.

This is due to the Mac doing the more computationally expensive rounding on each flight, then summing that. You would only see a difference between Mac and iPhone if you are using decimal time display, rounded to tenths, and you are entering total times NOT rounded to tenths. E.g. if you log actual out and in times and don't round them to the nearest 6 minutes then then the resulting value is not an exact tenth, and we always store precise to the minute. That way if you want to switch to see times in hours:minutes, you get the right values.

Technically the iPhone would currently have the more "accurate" value as it is adding up the sum of all your total times exactly as they are to the minute, then rounding the result to the nearest tenth. Whereas on the Mac we allow you to round every flight first then sum those; that is primary so that when you generate a printed report if you manually sum the columns when using decimal tenths format you get the right number at the bottom!

We are trying to think of the best solution going forward, we'd love to hear user feedback on this. Would you prefer to not have the Mac round the values except when generating reports? Would you like the iPhone to allow rounding at the expense of performance?

NOTE

If you switch to Hours:Minutes format or turn on 2 decimal places on the Mac then you'll get the same totals in both Mac and iPhone. Note that if you have had the values rounded you'll need to close and re-open the logbook to get the updated values.