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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dantje [Submitted to the original trac issue database at 6.14pm, Sunday, 23rd March 2008]
This makes it easier for me to follow confusing tracks and (manually) sync with audio.
Note that every trackpoint that does not have an explicit timestamp on import receives
the current time in its constructor. This is probably good when manually creating
nodes, for OSM downloads that don't offer a timestamp a invalid null timestamp might
be better.
The text was updated successfully, but these errors were encountered:
Author: koying [Added to the original trac issue at 4.35pm, Wednesday, 26th March 2008]
The usefulness of the information appears limited to me, but why not...
However, the fact that you are using screen estate for ALL points, with static information only interesting(?) for trackpoints is not acceptable.
In #675, I plan to have a specific dock for informational data (I was thinking about the OSM data, last user, last updated, ...).
This information will perfectly fit into this canvas.
If you want to get down with it, even only for trackpoints timestamp, you are welcome.
Reporter: dantje
[Submitted to the original trac issue database at 6.14pm, Sunday, 23rd March 2008]
This makes it easier for me to follow confusing tracks and (manually) sync with audio.
Note that every trackpoint that does not have an explicit timestamp on import receives
the current time in its constructor. This is probably good when manually creating
nodes, for OSM downloads that don't offer a timestamp a invalid null timestamp might
be better.
The text was updated successfully, but these errors were encountered: