Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding new vertices with coordinate cursor locked and map canvas not centered gives no indication something happened #5883

Open
suricactus opened this issue Dec 6, 2024 · 0 comments

Comments

@suricactus
Copy link
Collaborator

Describe the issue

When the coordinate cursor is locked the new feature vertices shall be added at the current location point. If a user moves the map canvas so the current location is no longer visible, and the user adds vertices, one cannot be sure if the vertex has been added or not.

Reproduction steps

Steps to reproduce the behavior:

  1. Open any project with line or polygon layer.
  2. Select a line or polygon layer and go to editing mode.
  3. Toggle the coordinate cursor to locked position.
  4. Move the map canvas so the current location is not visible.
  5. Click on the "Add vertex" button.

Expected behavior

Some kind of indication that adding vertex was successful. There are multiple approaches, I think they are all applicable::

  1. QField can show the number of vertices that were already been added to the currently edited geometry
  2. QField can show a toast message "Vertex #N has been added.". This might be annoying though.
  3. QField can recenter the map to the current location if a vertex has been added and the current location is not visible.

I think 3. can solve the immediate issue and 1. is nice to have for further UX improvement.

Observed behavior

There is no indication that a vertex has been added.

Screenshots and GIFs

video_2024-12-06_10-22-36.mp4

In the video you can also observe the #5882 .

Versions

Any QField version up to 3.4.x, QGIS and QFieldSync are irrelevant.

Additional information

  • Problem started happening recently, didn't happen in an older version of QField: No
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
  • Problem happens with all files and projects, not only some files or projects: Yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant