<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> Attempt to add nodes and reshape path ends up with losing control of the node tool. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - open example file - double-click blue object (it will select and then switch to node tool) - double-click path line to add a node - click-drag the node and move it around #### What happened? It moved the node a short distance and then starts misbehaving. If you release the mouse button it still has the path "grabbed" in an unexpected way. If you move the cursor over the path line it manipulates it with no mouse button pressed. If you select the green path (with no lpes applied) and move over the path it behaves like you grabbed the path itself itself too. #### What should have happened? It should handle the click+drag as expected. Sample attachments:  #### Version info <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` Inkscape 1.4-dev (1:1.4.0-dev+202403160151+300e768e46) ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->