Modify ↓
Opened 14 years ago
Closed 13 years ago
#6805 closed enhancement (invalid)
connecting ways does not always keep lowest id:
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | connect ways id | Cc: |
Description (last modified by )
Instead the id of the first selected way is used.
Attachments (0)
Change History (6)
comment:1 by , 13 years ago
| Description: | modified (diff) |
|---|---|
| Priority: | normal → major |
| Summary: | connecting ways does not always keep lowest id: → Regression: connecting ways does not always keep lowest id: |
comment:3 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
Or is this a feature as you can decide through selction which id to keep ?
comment:4 by , 13 years ago
| Owner: | changed from to |
|---|
comment:5 by , 13 years ago
Can you explain why it’s important which ID is kept? I read the API docs, but as far as I can tell the ID only serves as means to identify an object. All arguments I can think of to choose one ID over the other work both ways.
comment:6 by , 13 years ago
| Resolution: | → invalid |
|---|---|
| Status: | needinfo → closed |
| Summary: | Regression: connecting ways does not always keep lowest id: → connecting ways does not always keep lowest id: |
| Type: | defect → enhancement |
The ID was for my a quick info about the age of an object. Technically there is no differents.
Maybe it would have helped with the license change.
As noone else commented on this ticket, I will treat it as feature and close the ticket.
Note:
See TracTickets
for help on using tickets.
The regression was introduced with r3445.