Path Cursor Problems

What Wick Editor Version are you using?
Both 1.19.3 Web Version, and Stickmanred’s fork

Describe the Problem
I use the Brush tool to draw, and then I use the Path Cursor to make adjustments to the drawing to make up for lack of hand eye coordination.
Expected behavior: Double click the path object with the Path Cursor to view the path. Start clicking and dragging stuff to modify it, be it moving nodes or curves, adding/deleting nodes, and pulling on handles to adjust curves
Behavior I’m seeing: This is going to sound weird, but the above behavior only works if the path topologically has no holes (A straight line, for example). Anything with a hole (The outline of a circle, for example), the behavior becomes: Double click the path object with the Path Cursor to view the path. Click in any way shape or form, the path is deselected. As such, you can only do things that do not require selecting the path (remove nodes, move nodes, tug on curves and let them do their own thing).

What have you tried so far?
Tried different versions of Wick (web version, test version, stickmanred’s version), tried making the path object into a clip and editing the clip. Verified that making a gap in a non editable closed loop makes it editable, and closing the gap in a non closed loop (by merging) makes it no longer editable. Also tried multiple other softwares but Wick really is the best at what it does.

Do you have a Wick Editor File that we can see?
HandleTest3-28-2025_18-09-14.wick (4.0 KB)

(Edit: I am now allowed to upload attachments. Below was written prior)
I have one, but “new users can’t upload attachments”. Screenshot of file contents here, if you replicate my drawings you should be able to replicate my problem

If anyone has some insight on to whether this is a bug, or something I’m doing wrong, or a way to make things happen the way I want them to happen, it would be greatly appreciated!

2 Likes

I think you just found a Wick Editor bug! It seems to originate in this snippet of code, and I guess the developers didn’t get to it…

Right now, I can’t change anything in the fork, but I made a bookmarklet that should fix things: Link to Github The bookmarklet link is the text of the file

1 Like

You’re amazing! This worked perfectly and fixed the error both in the original 1.19.3 web editor, and your forked version as well.

Absolutely incredible, thank you.

1 Like