MerginMaps / MerginMaps/mobile
Position tracking lifecycle
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Problem / doubt:
When position tracking is started it appends geometry from a previous unfinished tracking if there is some. However, tracking time starts from scratch.
To reproduce:
- Open project with position tracking enabled
- Start the position tracking
- Close the App without stopping tracking
- Open the App and again - there is no evidence of tracking in progress, the unfinished tracking geometry is not visible
- Start the position tracking (in the same project)
- See the geometry was 'joined' from the unfinished tracking but the tracking time starts from 0.
https://github.com/user-attachments/assets/e4633019-3ae0-4db4-bdc6-fe14b60b17be
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the lifecycle described: begin position tracking, close the app without stopping, reopen the project, and start tracking again. Trace the position-tracking startup and resume paths to compare unfinished geometry visibility with elapsed-time restoration; done means both the pending tracking state and its time are handled consistently after reopening.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100