QGIS » QGIS Application

- snapping doesn't work properly with node tool

for snapping, it's mainly the visual feedback which is missing

My fault, I accidentally did this.

Actually, that last point is a dupe of #13099. Sorry for the noise!

I'm seeing this behavior with deleting nodes in a polygon:

- select a node, press delete
- QGIS starts MOVING the next node, and it's automatically relocated to the mouse position. move the mouse a bit and things go crazy with the rubberband.

The correct (2.8) behavior is that deleting a node just selects the next node, and doesn't automatically start moving it.

Another issue is:
- Select a node with left click, QGIS starts moving it
- Try to select the next node using > or < , the selected node changes but not for the rubberband - things go crazy

- Select a node with left click, QGIS starts moving it

This is the intended new behavior to allow advanced digitizing to be used with the node tool.

That's not the issue though - the issue is the rubberband doesn't cope with navigating through points using > and <

I'll try to make the point, as of today's master

• deleting a node: the rubber band is not removed
• deleting a node: when finished, the next node should be pre-selected (this pre-selection should by synchro with the table view selection model).
• pre-selection allows modifying coordinates in the table (keeps the same pre selection) or deleting the node (next node is then pre-selected)
• we can use < > in the pre-selection to browse nodes
• multiple nodes can be pre-selected (so they can be deleted at once)
• right-click should cancel the edition of the node (but keeps it pre-selected)
• right now, table view does not allow deletion (it should)
• for point layers, there is no visual feedback of the point being moved (no rubberband)
• cannot remove parts and rings or full geometries by removing all vertices (see #13099)
• editing in table view: changes should be applied to the rubberband on keypress (not on editing finished), and when editing is finished it should ends the digitizing (clear rubberband)

deleting a node: when finished, the next node should be pre-selected (this pre-selection should by synchro with the table view selection model).
pre-selection allows modifying coordinates in the table (keeps the same pre selection) or deleting the node (next node is then pre-selected)

What is 'pre-selected'? Is it a third state between not-selected and selected where the node is selected but the rubberband not moved?

• delete it
• move it by entering coordinates in the table view

• the selection of its corresponding row in the table view
• the end of a digitizing action (moving/deleting/inserting a node, in the case of deleting next available node is pre-selected)

Does it make sense to you?

The pre-selection of a node is triggered by:

the selection of its corresponding row in the table view
the end of a digitizing action (moving/deleting/inserting a node, in the case of deleting next available node is pre-selected)

Also by navigating through nodes using < and >

I would rephrase to:

• selecting a row in the table view
• pressing < or > to go to previous/next node

The idea of the pre-selection is that the node is selected but doesn't follow the mouse.
In such state, you can:

Ok, I understand. It is hard to tell how usable it will be before having it implemented. It needs quite a bit of changes in the node tool class (and tomorrow, I'm going to the FOSS4G conference...).

Also, pre-selection should allow multiple nodes selection to allow their deletion at once (otherwise, we have a regression).

Also, pre-selection should allow multiple nodes selection to allow their deletion at once (otherwise, we have a regression).

I believe it was also possible to move multiple nodes at once in 2.8. Not sure how that can be translated to the click click model, but let's add that to the fix list too...

I believe it was also possible to move multiple nodes at once in 2.8. Not sure how that can be translated to the click click model, but let's add that to the fix list too...

This is not straightforward in the click-click mode.
An idea could be to use the space bar to free pre-selected node(s).

Nyall Dawson wrote:

Also, pre-selection should allow multiple nodes selection to allow their deletion at once (otherwise, we have a regression).

I believe it was also possible to move multiple nodes at once in 2.8. Not sure how that can be translated to the click click model, but let's add that to the fix list too...

Absolutely, one could (quite conveniently) move a set of nodes at once. It was working like this:
- drag over a set of nodes to make your selection
- click and hold the mouse's left button on one of the selected nodes and drag

That would move a group of selected nodes, and the node through which your moving the group would respect snapping settings too.

Honestly... given the timing involved, huge number of regressions, and lack of developer presence, is it worth postponing the move to click-click to 2.14?