Modify ↓
Opened 9 years ago
Closed 9 years ago
#10019 closed enhancement (fixed)
Order of nodes in relations after unglueing
Reported by: | rayquaza | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.05 |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Yet another way to break a bus route: ;-)
- Create two ways (A and B) with a common endnode (N)
- Create a relation with the following objects: N, A, B
- Unglue the two ways
Usually one would now delete one of the doubled nodes (so it's no longer doubled). But have a look at the relation: It contains N1, A, B, N2. So you've got a 50% chance to delete the wrong node. A (hopefully) better result would be N1, N2, A, B.
Attachments (0)
Change History (3)
comment:1 Changed 9 years ago by
Milestone: | → 14.05 |
---|
comment:2 Changed 9 years ago by
Note: See
TracTickets for help on using
tickets.
In general it is a good idea to include the new clone members just below their origin.