#7673 closed defect (fixed)
merging nodes sometimes replaces known id with id:0
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | merge node id | Cc: |
Description (last modified by ) ¶
- 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.
Change History (7)
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
comment:2 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
just happened again merging a node with id onto a new one.
follow-up: 5 comment:4 by , 13 years ago
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 by , 13 years ago
Priority: | critical → 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.
In 5216/josm: