Opened 15 years ago
Closed 15 years ago
#3803 closed defect (fixed)
Splitting a way sometimes doesn't modify the original way
Reported by: | Daeron | Owned by: | Daeron |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
When a way is extended forming a loop in the end of the way by creating a new node to a middle of some of the segment in the way, and then adding the new node to selection, and then splitting, leaves the original way untouched.
The crucial step is to not deselect the way after extending it, but to add the newly created node to the selection. If you deselect the way between the extending and split, the bug won't appear.
Atteched is a simple osm-file that will allow the reproduction of this bug:
- Extend the way from the end to the middle of the first two nodes creating a fourth node
- Add the newly created node to the selection
- split the way
This will leave you with two ways, the original untouched, and a new closed way, but it should have left only a two-node way (first node and the new node), and the closed way.
Attachments (1)
Change History (3)
by , 15 years ago
Attachment: | extendsplit.osm added |
---|
comment:1 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:2 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | needinfo → closed |
It seems this was fixed in r2401
I can't reproduce. Either this is fixed or I can't follow your description. Does this still happen in newer latest?