Conversation
…henever tracking is suspended and then resumed
…ting a new segment by just going back to track list
jamescr
left a comment
jamescr
left a comment
There was a problem hiding this comment.
would be nicer that every point get associated with a consecutive segment number and not with 0 or 1 only. What do you think?
| @@ -125,7 +126,7 @@ public class DatabaseHelper extends SQLiteOpenHelper { | |||
| * v17: add TBL_TRACKPOINT.COL_ATMOSPHERIC_PRESSURE and TBL_WAYPOINT.COL_ATMOSPHERIC_PRESSURE | |||
| *</pre> | |||
There was a problem hiding this comment.
Update documentation:
* v18: add TBL_TRACKPOINT.COL_NEW_SEGMENT
There was a problem hiding this comment.
Thanks for your feedback
would be nicer that every point get associated with a consecutive segment number and not with 0 or 1 only. What do you think?
You mean, every segment? Yes, that would be another way to represent multiple segments.
The way the my proposal currently works is that the first point of each segment has 1 (or true), and all the following ones are false again. In a way, it is the derivative of the segment number.
However, if you have a strong preference for the other way, I can change it. However, in that case, I'll apply this to my later pull request (#312, "Import a gpx file as a route to follow"), because there is some interdependence among both. Also, please note that I will be on the move until end of August, and might not get back to this until then.
|
Alain thanks for this PR! Definitely is a great contribution |
|
Hi @AlainKnaff, thanks again for this PR! Currently, there are conflicts with the dev branch that need to be resolved before it can be merged. |
4 participants
Hi,
This pull request adds the possibility to have multiple segments per track ( tag in the XML file). Each time tracking is stopped and later resumed, a new segment is started. This helps avoid the clutter of unsightly lines crisscrossing the displayed track when position changes while tracking is stopped.
Thx for merging,
Alain