Trunk (maybe just a question): node insertion by double-click/snapping

[Hachmann]

In the release notes, I found this:

"When double clicking to insert new nodes, the position of these new nodes will snap to for example path intersections and to path-guide intersections"

and tried it out in the trunk version I have installed.

What happened was that the preview crosshair, that is supposed to show where the node is inserted, and the node position created by double-click match when there is nothing to snap to.

But when the crosshair is displayed on a snap target (i.e. a guide / path intersection), it's displayed in a different place than where the node is created on double-click (node is created as if snapping wasn't active, crosshair displayed correctly).

Is this a user error or a bug? Do we need to adapt the release notes?

=====
Related bug report/commit:
Bug #1448859: Make node tool snap to path intersection when adding node
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14189

[su_v (suv-lp)]

Hachmann wrote:
> (...) tried it out in the trunk version I have installed.
and
> (...) Do we need to adapt the release notes?

Just curious - what does a possible breakage in latest unstable trunk <lp:inkscape> have to do with the release notes for upcoming stable release (0.92) which is based in the stable release branch <lp:inkscape/0.92.x> ?

Could you attach a test case (SVG file) (ideally created with a recent build of <lp:inkscape/0.92.x>), describe the Inkscape snap settings in the preferences (if different from default), and the details wrt selected path(s) and the intersection intended to be used for positioning the inserted node?

[su_v (suv-lp)]

Not reproduced (node is inserted at path intersection) with latest lp:inkscape/0.92.x r15133 (on OS X 10.7.5), using default (i.e. new) preferences - example file attached.

[su_v (suv-lp)]

Test with nodes inserted at guide-path intersection.

[Hachmann (marenhachmann)]

@suv: It's good to read that it can't be reproduced with the 0.92 branch :)
There's no ppa for it, so I'm stuck with trunk, unless I want to set up an additional VM (and I don't have time for that right now). That's why this was a question - thanks for helping to answer it.

Then this appears to be a regression in trunk, to me, as with your file, I get the same results I described above.