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

Node editor as it works in 2.* #28669

Closed
qgib opened this issue Dec 19, 2018 · 6 comments
Closed

Node editor as it works in 2.* #28669

qgib opened this issue Dec 19, 2018 · 6 comments
Labels
Digitizing Related to feature digitizing map tools or functionality Feature Request Feedback Waiting on the submitter for answers

Comments

@qgib
Copy link
Contributor

qgib commented Dec 19, 2018

Author Name: Marc-André Saia (Marc-André Saia)
Original Redmine Issue: 20850

Redmine category:digitising


Hi

Versions 3 of Qgis and beyond use a new method of editing nodes that can be confusing for anyone who is used to working with Qgis for a long time. It would be interesting to be able to choose between the new method and the classic way.

@qgib
Copy link
Contributor Author

qgib commented Dec 19, 2018

Author Name: Giovanni Manghi (@gioman)


My opinion: it won't happen.


  • assigned_to_id removed Victor Olaya
  • subject was changed from Editing knots (vertex) in classic mode to Node editor as it works in 2.*
  • category_id was changed from Vectors to Digitising

@qgib
Copy link
Contributor Author

qgib commented Dec 23, 2018

Author Name: Corey Burger (@CoreyBurger)


I would say that we need something that merges the best of the 2.x with the new 3 method. There are major UI issues with the new node editing. Here is what I noticed:

  1. No difference between node hovered over and node selected (this is a MAJOR bug)
  2. Cannot select a different line or node on another segment with node tool
  3. Silently starts moving and adding nodes

All in all, I find the 3 version very hard to figure out what it is doing.

@qgib
Copy link
Contributor Author

qgib commented Jan 23, 2019

Author Name: Martin Dobias (@wonder-sk)


Corey Burger wrote:

  1. No difference between node hovered over and node selected (this is a MAJOR bug)

Hovered node has red, selected node has blue color. Or what did you mean? A screencast would help to clarify.

  1. Cannot select a different line or node on another segment with node tool

Please be more specific - what do you expect and what happens instead?

  1. Silently starts moving and adding nodes

Sorry I have no idea what do you mean here... it can only start moving/adding nodes when you click with mouse :-)

@qgib
Copy link
Contributor Author

qgib commented Jan 25, 2019

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jan 30, 2019

Author Name: Regis Haubourg (@haubourg)


Corey Burger wrote:

I would say that we need something that merges the best of the 2.x with the new 3 method. There are major UI issues with the new node editing. Here is what I noticed:

  1. No difference between node hovered over and node selected (this is a MAJOR bug)
  2. Cannot select a different line or node on another segment with node tool
  3. Silently starts moving and adding nodes

All in all, I find the 3 version very hard to figure out what it is doing.

Hi, most of the time, the hard part is to switch to the click-click mode instead of the clic and drag used before. Now I'm used to it, I have hard time when going back to 2.18. It's mostly a matter of habits. I've been doing data digitizing recently wiht students and didn't face anymore major issues. We can still polish it, and improve it's capabilities to interactively grab features (the worst point currently IMO) and snap to others features. Let's push screencasts so that we can help you

@qgib qgib added Feedback Waiting on the submitter for answers Feature Request Digitizing Related to feature digitizing map tools or functionality labels May 25, 2019
@nirvn
Copy link
Contributor

nirvn commented Nov 7, 2019

I think this can be closed. If the vertex editor hasn't reached perfection yet (:wink:) please file individual issues for each problematic UI/UX point that would need addressing.

@nirvn nirvn closed this as completed Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Digitizing Related to feature digitizing map tools or functionality Feature Request Feedback Waiting on the submitter for answers
Projects
None yet
Development

No branches or pull requests

2 participants