Closed GoogleCodeExporter closed 9 years ago
Ditto this. For example when entering into a store one would want to pause and
then resume afterwards. I also casually map when I'm travelling and oftentimes
it would be convenient to be able to pause.
Original comment by jesperfj...@gmail.com
on 25 Jul 2010 at 9:15
Since revision #270 adds the possibility to resume any track from the
TrackManager, it is possible to stop the track and resume tracking at any time.
best regards
Matthias
Original comment by matthias...@gmail.com
on 19 Dec 2010 at 11:44
I just tested it and when resuming track when there is already an active track
the trackpoints are still tracked with the previous track id (However the way
points are correctly recorded for the resumed track).
This can be seen using the DDMS log, for example:
* Create a new track (id 43)
* Record some location (trackpoints)
* Back to track logger, and resume an old track (id 40), while the id 43 is
still active. Click "start tracking" in the menu
* You get the following log when recording a location:
01-03 14:55:50.696: VERBOSE/DataHelper(718): Tracking (trackId=43) location:
Location[mProvider=...]
01-03 14:55:50.716: VERBOSE/TrackContentProvider(718): insert(),
uri=content://me.guillaumin.android.osmtracker.provider/track/43/trackpoints,
values=[...] track_id=43
* And the following log when tagging a waypoint:
01-03 14:55:56.816: VERBOSE/GPSLogger(718): Received intent
me.guillaumin.android.osmtracker.intent.TRACK_WP
01-03 14:55:56.826: VERBOSE/DataHelper(718): Tracking waypoint 'Attraction',
track=40, [...]
01-03 14:55:56.856: VERBOSE/TrackContentProvider(718): insert(),
uri=content://me.guillaumin.android.osmtracker.provider/track/40/waypoints,
values=[...] track_id=40
Original comment by nicolas@guillaumin.me
on 3 Jan 2011 at 4:00
Nicolas,
thanks, i didn't realize this.
In r274, a "STOP_TRACKING" broadcast is sent when a new active track is set, to
be sure GPSLogger stops a recording of another track that could be active at
this moment.
best regards
Matthias
Original comment by matthias...@gmail.com
on 4 Jan 2011 at 12:45
Original issue reported on code.google.com by
nguillau...@gmail.com
on 11 Apr 2010 at 1:26