Tool: Reshape
You’ve drawn a long, sweeping line — the back of a letterform, the edge of a leaf, the top of a hill. It’s nearly right. But it sags. Somewhere through the middle third it dips lower than it should, and you want to lift that section about four pixels.
So you reach for the pen, and you look for the anchor that’s wrong.
There isn’t one.
That’s the whole problem, and it’s worth sitting with, because it is the moment where most people’s mental model of vector drawing quietly fails them. The sag isn’t located at an anchor. It’s a property of a stretch of the curve — an emergent consequence of two anchors and their four handles, none of which is individually incorrect. If you grab the nearest anchor and pull it up four pixels, you don’t lift the sag. You put a bump next to it. The sag is still there, and now there’s a bump.
You can fight this. People do. You nudge an anchor, then compensate on its handle, then the neighbouring segment goes strange so you nudge that, and twenty minutes later you have a curve that is wrong in four new places and you have forgotten what the original problem was. I have done this more times than I want to admit, and every time the fault felt like mine, and it wasn’t. It was the tool’s. I was being made to fix a regional problem with a pointwise instrument.
Reshape is the regional instrument. You rubber-band a region of the path — not an anchor, a stretch — and you drag, and the whole stretch moves. The anchors inside your selection travel with you. The ones outside stay put. And crucially, the segments in between don’t kink at the boundary: the transition is graded, so the influence falls off, and the curve stays smooth where it hands back over to the part you didn’t touch.
You grab the sag. You lift it. It’s lifted. Four seconds.
The reason I find this tool interesting is not that it saves time, although it does. It’s that it corrects a category error that the tool itself created. A curve, to you, is a continuous thing. A curve, to the document, is a list of anchors. Those are different objects, and for most of the history of vector drawing, the editing tools have belonged to the document’s ontology rather than yours. You are allowed to move an anchor because an anchor is a thing that exists in the data structure. You are not allowed to move “the sag” because the sag isn’t in the file. [1]
But the sag is in your head, and your head is what’s doing the drawing. A tool that can only manipulate the things in the file is a tool that forces you to translate every intention into the file’s terms before you can act on it. That translation is exactly the twenty minutes.
So Reshape is one of a small number of tools I’d point to as evidence that a vector editor doesn’t have to be a thin veneer over an SVG path. The path is how the drawing is stored. It shouldn’t dictate how the drawing is touched.
Smooth is its cousin, and worth knowing the difference. Both act on regions rather than points. Smooth takes the tremor out of a stretch and leaves it where it is. Reshape takes a stretch and moves it. One fixes quality; the other fixes position. When something looks wrong, ask which — you’ll usually know immediately, and reaching for the wrong one is why the curve keeps not getting better. [2]
[1] Photoshop’s warp tools have always known this — you push pixels around in regions, because nobody imagines a photograph as a list of coordinates. The vector world took much longer to get there, I think because its data structure is so legible that it’s tempting to just expose it and call the job done.
[2] There is a third possibility, which is that the curve is wrong because it has thirty anchors and should have four. No regional tool fixes that. Smooth it first, then reshape what’s left; trying to reshape a lumpy path just moves the lumps.