InsertControlPoint doesn’t work but you can remove the points - as long as the resulting boundary won’t self-intersect… Except not always, I encountered hatch control points that should have been fine to remove but still refused to be deleted.
Unfortunatelly, there are more issues with hatches:
performance and reliability
Hatch creation by clicking inside boundary can get terribly slow (performance-wise) and unreliable when working inside complex drawings. I’ve learnt, it is often better to first use the awesome CurveBoolean tool because it is faster and it will also fill spaces that the hatch command (by boundary) will refuse to fill! (I guess these tools do not share the same alghorhitms under the hood, maybe that is changing now?)
coordinate space
The behaviour of hatches inside blocks is problematic:
- open the block in a different position to where it was created
- do not even touch the hatch
- save the block
- the hatch will shift its origin point, or even change the rotation
This makes it problematic to utilize blocks, eg. for subdividing floorplans into apartments or rooms, because hatches (other than solid) will loose alignment once the blocks are edited indpendently.
scaling
in one direction changes the rotation of the hatch. One has to manually reenter the original numeric value of rotation again. Why is that?
mirroring
is probably connected:
- select several hatches
- assign the same rotation to all of them, eg. 45 degrees
- get surprised that some of the hatches lean on the wrong side - they are rotated by 90 degrees compared to the rest …because they were created by mirroring
gradient hatches
are so unreliable I tend to avoid them - often, they will not show up in the exported PDF. It makes me very sad as this would be great capability for infographics, diagrams etc.
