try to re-create the arrows here https://i.imgur.com/2h0h67F.png in the order implied, arrow 4 is practically impossible to create (because instead it thinks you want to edit arrow 3)
I've run into this issue too. Is it possible for the arrows to only count their "hitbox" on the actual space of the arrows, rather than it's containing box?
There is a way to calculate exact hit box of shape but for performance concerns I was instead used rectangle. Solution should be again using rectangle but rotated one to fit arrow shape but it would require knowing trigonometry.
Another possible "solution", wouldn't be as elegant, but have a button or something that toggles whether you can actually move or target the other arrows after you've placed them, and only let you place new ones.
One workaround for this issue is hold mouse click outside and hold ctrl to move it while creating arrow.
@Jaex obviously not ideal, but indeed it works!
@Jaex I assume a normal box is being used for the arrows instead of a minimum bounding box?
This may be helpful if that's the case: https://gist.github.com/douglasg14b/98023ded67c61369709e5b82b8ffba46
I made this for a receipt parser, and I'm pretty sure it worked and doesn't require any dependencies (Point or PointF might be an Emgu dependency?), it was made quite a while ago so my memory may be rusty.
Reason for using rectangle bounding box is performance.
Most helpful comment
One workaround for this issue is hold mouse click outside and hold ctrl to move it while creating arrow.