#7673 closed defect (fixed)
merging nodes sometimes replaces known id with id:0
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | latest | Keywords: | merge node id |
| Cc: |
Description (last modified by skyper)
- download some data
- create a new node
- move a node with id over new one and merge using Ctrl
The merged node has id:0 instead of the already existing one.
This leads to many unneeded creations and deletions of nodes plus changes in ways and breaks the history of nodes.
Attachments (0)
Change History (7)
comment:1 Changed 13 months ago by skyper
- Description modified (diff)
comment:2 Changed 13 months ago by Don-vip
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 12 months ago by skyper
- Resolution fixed deleted
- Status changed from closed to reopened
just happened again merging a node with id onto a new one.
comment:4 follow-up: ↓ 5 Changed 12 months ago by skyper
Please, could this get fixed before releasing a new tested version.
This bugs makes the license change not easier and hides some problems.
Thanks
comment:5 in reply to: ↑ 4 Changed 12 months ago by skyper
- Priority changed from critical to major
Replying to skyper:
Please, could this get fixed before releasing a new tested version.
This bugs makes the license change not easier and hides some problems.
Thanks
I did test again and the major problem is fixed but the merged node is not selected and the selection toggle dialogue is not adjusted.
comment:6 Changed 12 months ago by bastiK
- Resolution set to fixed
- Status changed from reopened to closed
In 5265/josm:
comment:7 Changed 12 months ago by skyper
Thanks



In 5216/josm: