MerginMaps / MerginMaps/mobile

Crosshair freezes and does not move to last vertex immediately after removing recorded geometry at zoom level 20m

Open
#4,613 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug map tools
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Description

When the map is zoomed in to 20m zoom level and the user is recording a LineString or MultiLineString geometry and removes a recorded vertex, the crosshair does not immediately snap back to the last remaining vertex. Instead, the crosshair remains frozen in its current position while the line is removed. After a short delay, the crosshair eventually moves to the correct position of the last vertex.

Environment

[x] Staging

Application (+ app version, build, operating system)

Dev/OS/App IPhone 15 / iOS 26.0 / MM 2026.3.0 - 26.7.927811

Steps to reproduce

  1. Open a project containing a LineString or MultiLineString layer.
  2. Tap Record and select the line layer.
  3. Zoom in to 20m zoom level.
  4. Add several points to create a line geometry.
  5. Tap the Remove last vertex button to remove the recorded geometry/vertices.
  6. Observe the position of the crosshair immediately after removal.

Actual results

The crosshair does not immediately move to the last remaining vertex after removing the recorded geometry. It remains frozen in its current position for a short period. The line vertices are removed correctly, but the crosshair movement to the last vertex is delayed.

Expected results

The crosshair should immediately snap back to the position of the last remaining vertex as soon as the recorded geometry is removed, with no delay.

Screenshots or logs

https://github.com/user-attachments/assets/537dde95-bb3e-4bf8-84e4-1210921e163d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue on iOS with a LineString or MultiLineString at the 20m zoom level, then trace the recording flow after Remove last vertex is tapped. Verify that the crosshair update follows geometry removal immediately; done means it snaps to the last remaining vertex without the observed delay.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, ios
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.