Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Gimp 3 path tool auto connections.
#1
In gimp 3 I'm finding it a pain when trying to move an end anchor of an open stoke, something I do a lot.  All the extra shift clicking to deselect the prior end anchor to stop the path tool making unwanted connections is impractical for anything other than simple paths.

I was so desperate I even read the manual:
https://docs.gimp.org/3.0/en_GB/gimp-tool-path.html
"To quickly close the curve, click on the initial control point. If you want to reposition the start node, hold Shift and click to deselect the end node, then move the start node."

Can the auto connection be turned off?

   
Reply
#2
Maybe just a change in workflow. Shift key to start a new path.

This a little leaf video - adding a couple of paths - Layer mask from a path (via selection) - Translate (scale / rotate / move) the layer+mask+paths. https://sendvid.com/bvcivoa4

Not much different from Gimp 2.10 except for the vector layer. Looks like you can not link more than one path for the vector layer, but I am just a beginner with this.
Reply
#3
teapot: Auto-close on click was implemented after we received this issue report: https://gitlab.gnome.org/GNOME/gimp/-/issues/7715, which showed that multiple other art programs automatically close the path when you click on the start node.

We're looking to improve the Path tool now that we have vector layers (for instance, by having the ability to drag a selection box over the path and select multiple nodes at once), so we can definitely look into satisfying both workflows. Perhaps we could switch the toggle from 2.10 so that holding Ctrl lets you move the start node without selecting it?
Reply
#4
(11-20-2025, 12:59 PM)CmykStudent Wrote: teapot: Auto-close on click was implemented after we received this issue report: https://gitlab.gnome.org/GNOME/gimp/-/issues/7715, which showed that multiple other art programs automatically close the path when you click on the start node.

We're looking to improve the Path tool now that we have vector layers (for instance, by having the ability to drag a selection box over the path and select multiple nodes at once), so we can definitely look into satisfying both workflows. Perhaps we could switch the toggle from 2.10 so that holding Ctrl lets you move the start node without selecting it?

I found the CTRL+click in 2.10 much better, and like Teapot, I always unintentionally close the path, and after that spend a few second to remember how to do it correctly. But yes, if CTRL can be used for moving the initial node, I could adapt my workflow easily. For the context, it's rare that I regret old functionalities of the software, but in this one particular case, I do.

P.S: how about a much more natural behaviour combining both: only close the path on mouse release, and if the mouse moves, just move the node instead?
Reply
#5
(11-20-2025, 09:50 AM)rich2005 Wrote: Maybe just a change in workflow.  Shift key to start a new path.

This a little leaf video - adding a couple of paths  - Layer mask from a path (via selection) - Translate (scale / rotate / move) the layer+mask+paths.  https://sendvid.com/bvcivoa4

Hi Rich,

Thank for your reply and video.

As you did, I made each stroke in the veins path with shift-click.

The issue is when it's not a demo, having made the path, I will be wanting to move each anchor of the veins, often several times, until I'm happy with the design. This moving is often done zoomed a long way into the image for precision. The veins are open strokes and thus the auto-connect on click occurs unless you deselect any selected end-anchor first. After the 90th time of doing this the novelty wears off (I got to 90 after moving each of the 18 end-anchors just 5 times each and that's just one leaf).

To try it, zoom in until you can just see a couple of the vein's anchors and move each anchor individually.  Clearly that's an easy case, in real life you would be mixing moving end-anchors with other things so do you always deselect the last end-anchor just in case, or do you do other path-y stuff and check for an active end-anchor, possibly out of view, just before a move?



Hi CmykStudent,

Thank you for your reply and thank you for all the work you do for gimp.

(11-20-2025, 12:59 PM)CmykStudent Wrote: teapot: Auto-close on click was implemented after we received this issue report: https://gitlab.gnome.org/GNOME/gimp/-/issues/7715, which showed that multiple other art programs automatically close the path when you click on the start node.

Thanks, it's really useful to know what prompted the change, the issue report says:

Quote:The use case where you might want tweaking the start node before closing the path seems a little off. If specialized vector graphics apps mostly don't do that, why would GIMP with its less powerful vector tools do that?

This argument is flawed as it's only looking at one element of the path tool's user interface without considering how it affects other parts. It ignores what happens to the UI for open strokes.

In fact auto-connect on click has made gimp less like inkscape rather than more as inkscape's node tool has the same operation to move any node in the path, left click and drag, regardless of if it's an end node and there's another end node active or not. A quote from page 96 of inkscape's beginner's guide:

Quote:A path’s shape can be changed radically by moving the nodes it consists of:
1. Activate the Node tool.
2. Click on the path to select it.
3. Click and drag the node you wish to reposition

(11-20-2025, 12:59 PM)CmykStudent Wrote: We're looking to improve the Path tool now that we have vector layers (for instance, by having the ability to drag a selection box over the path and select multiple nodes at once), so we can definitely look into satisfying both workflows. Perhaps we could switch the toggle from 2.10 so that holding Ctrl lets you move the start node without selecting it?

Sorry no. A piecemeal approach would be swapping one mistake for another.

For example, the user may want to select an end-anchor e.g. ctrl-click to drag out a handle as is done for all anchors in gimp 2.10. At present in gimp 3 that also causes an unwanted auto-connect when it's an end-anchor and there's another end-anchor selected, possibly out of sight. This operation should remain the same for all anchors.

The operation to move an anchor/node should be the same regardless of where the anchor fits into the path.
  • When concentrating on finessing a path the user moving anchors should not have to distinguish between if they are end-anchors of an open stroke or not.

  • It's surprising behaviour to have end-anchors of open strokes behave differently to other anchors depending on what other anchors are active.

  • For an efficient workflow, moving any anchor should be simple.

  • Left click and drag is the standard way to move any node/anchor in both gimp 2.10 and inkscape.

So given the conflict between wanting auto-connect on click and wanting the same operation for moving any anchor I suggest gimp's 2.10 approach is best because:
  • Moving anchors is done far more often than closing strokes.

  • It preserves the muscle memory of current users, lowering the 2->3 upgrade hurdle.

  • Pressing ctrl when clicking to close a stroke isn't onerous. If people forget how there's always a hint in the bottom status bar.

  • 2.10 has a comprehensive path tool UI.

If this is disappointing for users who only use closed stokes, e.g. the use of paths to make a selection around an object they wish to cut out, then making the auto-connect a tool option so it can be turned on/off would be better than compromising the integrity of the path tool's UI.

In the above issue, I noticed this one which Bruno has closed writing:

Quote:Since this change was done in response to a issue, this is a resolved matter. Closing as out of scope.

If I put an issue in will it just get closed too? (I'm teapot over there BTW).

PS: There's currently a long thread of drawing with paths on gimpchat in which many images use open strokes, e.g. this by Issabella.

I asked about the gimp 3 path tool UI on the thread here but the replies here and here show those users are not using gimp 3 but are OK with the 2.10 path tool UI.
Reply
#6
teapot: Thanks for the detailed information! I think I have a better understanding now.

Regarding "In fact auto-connect on click has made gimp less like inkscape rather than more as inkscape's node tool", I think that's where the tension lies. If you asked me what GIMP's Path Tool was most similar to in Inkscape, I'd actually say the Pen Tool. Both of those create new edges and vertices, while Inkscape's Node Tool only edits existing ones. That's probably why people coming from other software get confused - the Path Tool acts like other software's Pen Tool in many cases, except it doesn't auto-close when you click on the end node.

However, GIMP does show the intermediate nodes and you can move them even in "Design" mode, which does differ from other software's Pen Tools. My knee-jerk reaction is that since Ctrl switches to Edit mode, which maps more closely to Inkscape's Node Tool in that you're working on an existing path, setting Ctrl to move the endpoint would be an improvement over the current situation. But as we've seen, going with knee-jerk responses can cause problems. Smile

Bruno is sometimes quick on the draw regarding closing issues, but that's because he tries to keep our issue tracker as clean as possible. He moved the issue to our UX tracker (Paths Tool, broken productivity (#760) · Issue · Teams/GIMP/Design/gimp-ux), but I think it didn't reopen automatically when he did. You could post your feedback there and it should restart the discussion.
Reply
#7
(11-24-2025, 04:34 PM)CmykStudent Wrote: teapot: Thanks for the detailed information! I think I have a better understanding now.

Regarding "In fact auto-connect on click has made gimp less like inkscape rather than more as inkscape's node tool", I think that's where the tension lies. If you asked me what GIMP's Path Tool was most similar to in Inkscape, I'd actually say the Pen Tool. Both of those create new edges and vertices, while Inkscape's Node Tool only edits existing ones. That's probably why people coming from other software get confused - the Path Tool acts like other software's Pen Tool in many cases, except it doesn't auto-close when you click on the end node.

However, GIMP does show the intermediate nodes and you can move them even in "Design" mode, which does differ from other software's Pen Tools. My knee-jerk reaction is that since Ctrl switches to Edit mode, which maps more closely to Inkscape's Node Tool in that you're working on an existing path, setting Ctrl to move the endpoint would be an improvement over the current situation. But as we've seen, going with knee-jerk responses can cause problems. Smile

Bruno is sometimes quick on the draw regarding closing issues, but that's because he tries to keep our issue tracker as clean as possible. He moved the issue to our UX tracker (Paths Tool, broken productivity (#760) · Issue · Teams/GIMP/Design/gimp-ux), but I think it didn't reopen automatically when he did. You could post your feedback there and it should restart the discussion.

Thanks for your engagement on this CmykStudent.

I'd say gimp's path tool is a subset of inkscape's pen tool plus node tool.  It makes sense for inkscape to split path editing into a separate tool as many tools create paths and the node tool is common to edit all of them.  The split of functions between design and edit is very different in gimp than inkscape though.

I have put my comment on the issue as you suggested.

Having read more on vector layers here, where I see you credited:
https://www.gimp.org/news/2025/09/01/gim...tor-layers
they do look cool especially in automatically updating when the path is edited, so again thank you.

I'd like to use the new features but can't if fundamentals inhibit upgrading.
Reply
#8
Quote:Bruno is sometimes quick on the draw regarding closing issues
Indeed....
And always this "out of scope" .... doesn't encourage a normal user to do bugreports anymore.
We take our time to do it well ... and it's closed after minutes ...
Hmmmm ....
Reply
#9
I don't know how to get the issue reopened,it looks pretty buried to me.
Reply
#10
teapot: Sorry, I don't have report status of the UX repo (just the code repo), or I'd reopen it myself. I'll make a post in a bit and see if that moves the needle.
Reply


Forum Jump: