bulia byak wrote:
I think this was considered undesirable when it was getting in the way while transforming objects - I remember it resulted in some erratic behavior then. But when limited to Node tool, I think it's useful, and in fact there it is even more useful than snapping to other paths' nodes, if only because we can still only edit one path at a time, which means that path's nodes are visualized and others' are not.
Snapping to nodes does not depend on the visibility of the nodes, neither for the selector tool nor for the node tool. So while editing one path, we can snap to the invisible nodes of other paths.
We currently have a mechanism to avoid "self-snapping" for objects, which works nicely now. In fact this mechanism is basically no more than just passing a list of objects which should not be snapped to. When in node tool however, we similarly need to pass the location of the node that is being dragged and should not be snapped to. I've just tried to make the node tool snap to it's own nodes, but it's now also "self-snapping" to the node being dragged... This is the same erratic behavior we saw way back while transforming objects. I'll have to fix that before committing a patch, so I won't make it tonight ;-)
Diederik