Trunk (maybe just a question): node insertion by double-click/snapping
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
New
|
Undecided
|
Unassigned |
Bug Description
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:/
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?