Closing object while dragging - other node affected
- 
					
					
					
					
Draw a simple shape with the pen tool. Attempting to close the curve by clicking the start node, holding button pressed and then dragging to make a curved line and this happens. Happened to me many times when hand tracing.

 - 
					
					
					
					
This is what I am trying to do:

Pssst: Note the elegant little cross, visual feedback, that indicates that clicking here will close the curve.
 - 
					
					
					
					
@Ingolf I think it just has to not be clunky.... elegant and subtle
Instead of a cross it could be a small faint circle for example
 - 
					
					
					
					
@Boldline said in Closing object while dragging - other node affected:
@Ingolf I think it just has to not be clunky.... elegant and subtle
Instead of a cross it could be a small faint circle for exampleA faint outline could work, yes.
 - 
					
					
					
					
@Ingolf I will try to improve this part.
 - 
					
					
					
					
@Ingolf There is a better indication of closing in the Pen tool, in build 1.1.024
 - 
					
					
					
					
@vectoradmin said in Closing object while dragging - other node affected:
@Ingolf I will try to improve this part.
Any luck with the closing curve affecting (removing) the second node created?
 Happens in some scenarios and not others, but I see it very often.
 - 
					
					
					
					
@Ingolf I cannot replicate this in the latest build. I keep the issue open.
 - 
					
					
					
					
@vectoradmin said in Closing object while dragging - other node affected:
@Ingolf I cannot replicate this in the latest build. I keep the issue open.
Last GIF was from latest build on Windows 10. This one is from macOS just now:

 - 
					
					
					
					
@Ingolf and @vectoradmin Replicated here also: https://recordit.co/SWgGkp0Qss
If you click-and-drag when creating the last node before closing the path, the first two segments get collapsed into one segment.
 - 
					
					
					
					
@b77 Replicated! Added to the backlog.
 - 
					
					
					
					
@Ingolf This problem should be fixed in build 1.1.048