Opened 6 years ago
Closed 5 years ago
#17683 closed enhancement (fixed)
RemoteControl Zoom Select maintain specified order of selection
Reported by: | EdLoach | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 20.03 |
Component: | Core remotecontrol | Version: | tested |
Keywords: | Cc: |
Description
If I send a command such as this one (as shown in the console window):
2019-05-06 01:02:15.759 INFO: RemoteControl received: GET /zoom?left=0&right=0&top=0&bottom=0&select=n474893791,n474889962,n474889958,n474896015,n474889953,n474889951,n474889947,n474889944,n474892703,n474893755,n474889991,n474892706,n474892717,n474892716,n474892714,n474892713,n474892710,n474892809,n474895884,n474892807,n474893158 HTTP/1.0
then all 21 nodes are selected, but seemingly in a random order. For example, if I try to add them to a new relation (to be a bus route relation) then they aren't in the order specified and I may as well select them all manually - not so bad for a short route like this one, but a bit time consuming for longer ones.
Attachments (0)
Change History (3)
comment:1 by , 6 years ago
comment:2 by , 5 years ago
Milestone: | → 20.03 |
---|
Selections are in fact ordered, see org.openstreetmap.josm.data.osm.DataSelectionListener
– everywhere a LinkedHashMap
is used. The order is used for various commands and the relation editor.
Selection has no order at all. And we won't add such a notion.
I guess what you would like is a remote control command that creates or modifies a relation. I don't think we have one atm.