Is there some logic to when “Trip Data” metrics like “Trip Time,” “Total Ascent”, etc. stop and start in the 67i “Trip Computer”. Some metrics stop when track recording is paused. Others continue to run. Some start running when Expedition Mode is entered and stop when the 67i leaves Expedition Mode even when Track Recording is turned off. The bottom line is that the “Trip Data” metrics are a mess in situations where the user is using Expedition Mode or pausing trip recording, e.g. on multi-day hikes. In my opinion all “Trip Data” metrics should be tied to track recording, i.e. they should correctly match the metrics of the track being recorded. They should stop if and only if track recording is paused or stopped and should start if and only if Track Recording starts or resumes.
