-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
on screen snapping indicator #23060
Comments
Author Name: Matthias Kuhn (@m-kuhn) Nice input! My ideas are:
For extra points, let the user page through the possible snapping results with a key. |
Author Name: Donovan Cameron (@saultdon) I think a great improvement would be also to see where the first click was! Like a large circle and then, maybe an auto-closing/complete feature so the user doesn't have to sniper the first vertex they clicked on. I usually have to zoom right in, super close to finish the edit and click on the first vertex or intersection I clicked on. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Regis Haubourg (@haubourg) Assigned to Martin, feature will be funded by QWAT's team
For example, the cursor could change to show if it's a vertex/node, segment or intersection and a small text popup showing what layer it's snapping to as well. to It'd be really nice if there was some kind of visual indicator telling the user what is being snapped. For example, the cursor could change to show if it's a vertex/node, segment or intersection and a small text popup showing what layer it's snapping to as well. |
Author Name: Giovanni Manghi (@gioman) Regis Haubourg wrote:
very nice, much appreciated! |
Author Name: Martin Dobias (@wonder-sk) Added in #5451
|
Author Name: Donovan Cameron (@saultdon)
Original Redmine Issue: 15119
Redmine category:digitising
Assignee: Martin Dobias
It'd be really nice if there was some kind of visual indicator telling the user what is being snapped.
For example, the cursor could change to show if it's a vertex/node, segment or intersection and a small text popup showing what layer it's snapping to as well.
The text was updated successfully, but these errors were encountered: