Modify ↓
Opened 13 years ago
Closed 13 years ago
#3755 closed defect (fixed)
ctrl+drop node merging doesn't use destination node coords
Reported by: | Ldp | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | node merge ctrl | Cc: |
Description
When merging nodes, using ctrl + dropping the node on another, it doesn't use the coordinates of the destination.
From some observations, I think it is currently finding the lowest (positive) node id, and using those node coords as the merged node location. It should always use the coordinates of the (destination) node.
This used to work fine some months ago.
I'm using 2300.
Attachments (0)
Change History (2)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Of course, by lowest node id, I mean the lowest node id of the nodes involved in the merge. Not the lowest node id in the entire loaded dataset.