You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes this looks like an oversight; I'm sure this issue is also in v1.8.
IIRC I did have a concern about performance if the time display option was set to 'World' as it might need to recalculate the timezone for every display update - which might be relatively slow - but the code works out the timezone as used in the Statistics display anyway (i.e. only on initial dialog opening).
Unfortunately it simply appears I forgot to change this bit.
Note the timezone can effect the date itself, so needs to be used more widely:
.Time related graphs
.Track & Waypoint lists
.Embedded graph tooltip
.Layers tooltips
…isplays
Note the timezone can effect the date itself, so needs to be used more widely:
.Time related graphs
.Track & Waypoint lists
.Embedded graph tooltip
.Layers tooltips
There's the following scenario as:
Preferences
I haveUTC
set as theTime Display
UTC
(as GPX generally does)If I open the track properties, the Start and End times are correctly shown in

UTC
:Yet if I change to the

Distance-Time
orElevation-Time
tabs, the times are displayed in local time (+2 hours):My system-wide timezone is indeed CET/CEST, but shouldn't viking show also these data in UTC, if the Preferences have that set?
Haven't checked yet with v1.8, the above happens with v1.7.
Thanks.
The text was updated successfully, but these errors were encountered: