Anchor + control affordances for the selected paths, bottom → top.
Returns two affordances rather than one so that a control handle beats
an anchor regardless of which is nearer — the same preference hitAnchor
encodes, and the same one the rendering has (controls draw on top). Within
each of the two, nearest wins. They deliberately share one id: chrome-caps
gates anchor editing as a single piece of chrome, and splitting the id
would invent a visibility rule nothing asked for.
Order matters — spread this into an affordance list in the returned order.
Anchor + control affordances for the selected paths, bottom → top.
Returns two affordances rather than one so that a control handle beats an anchor regardless of which is nearer — the same preference
hitAnchorencodes, and the same one the rendering has (controls draw on top). Within each of the two, nearest wins. They deliberately share one id: chrome-caps gates anchor editing as a single piece of chrome, and splitting the id would invent a visibility rule nothing asked for.Order matters — spread this into an affordance list in the returned order.