The prev solution was to clean up the tracker points before the new track recording starting.
It was not fully correct solution because:
1. it causes the bug, when if we starts a recording, the `TrackRecordingUpdateHandler` is called by subscribers but receives the old `track info` from the previous track. It happens because the starting is an async call and it cleans up the gps collection a little bit later.
2. when the user finishes the track recording the collection is not properly cleared. The data will stay in the memory `forewer` until the next recording is started. And this data will be recovered on the next app launch too. There are no reason to store all the recorded data in memory until the new recording begins. This approach was Ok for the `previous path` feature (removed) but not for the TR. The data lifecycle for the both feature should be handled separately.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
This implementation follows iOS version as much as possible and uses the same core logic.
Resolves#10081
Signed-off-by: Alexey Krasilnikov <alexey@krasilnikov.me>
Fixes the following warning:
````
map/framework.cpp:2252:12: warning: variable ‘rect’ set but not used [-Wunused-but-set-variable]
````
Signed-off-by: Ferenc Géczi <ferenc.gm@gmail.com>
To retrieve as a `GpsTrackInfo` struct that will be used to notify the UI about the track recording process.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
GpsTrackCollection has two methods to add: point and points.
The first one is used only once time in the unit test and removed to simplify the adding logic.
RemoveUntil is not used.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
The GetAddress is changed to the GetSecondarySubtitle because the 4th line in the header contains address for bookmarks or distance+duration for tracks
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
1. pass point with coodinates explicitly instead of calc the point by distance on every selection update
2. removed default track selection because the tracks should not have default marks
3. remove isInteractive property because all tracks are interactive now
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
1. filling ElevationInfo with data properties is removed because there is no such data for tracks in the data
2. elevation profile is initialized only with the MultiGeometry because it shouldn't know about any other info exept the lengths, altitudes and timestamps
3. data is calculated as concatenation of all geometry segments (not the 1st one as in old implementation)
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
* [platform] add ProductsConfig
1. fetch and parse ProductsConfig json
2. save it to the separate file "products_settings.json"
3. small servers_list.cpp refactoring
4. add unit tests for servers config and products config
5. add products fetching to the framework
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
Because of the `RecentPath` feature was replaced with the `TrackRecording`
the the file's tail shouldn't be truncated by the system. User can record
track for more than 24h. This is why the `Duration`, `TruncFile` and `m_maxItemCount`-rleated code
was removed.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
