Changes between Initial Version and Version 1 of Ticket #19581


Ignore:
Timestamp:
2020-07-26T17:22:19+02:00 (4 years ago)
Author:
skyper
Comment:

Fix does not work at all.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19581

    • Property Summary Wrong selection after merging nodes using "fix" buttonFixing duplicated nodes does not work
  • Ticket #19581 – Description

    initial v1  
     1**Edit:** Oh, the fix does not work at all but selection issue below is strange.
     2
    13==== What steps will reproduce the problem?
    241. Have two areas with `Mixed type duplicated nodes` ([attachment:josm_Mixed_type_duplicated_nodes_example.osm.xz josm_Mixed_type_duplicated_nodes_example.osm.xz])
    351. Run Validator
     61. Take a look at the number of duplicated nodes reported
    471. Select the nodes using select button in validator panel
    581. Take a look at the selection in selection list panel (2 nodes)
    691. Click on fix button in validator panel
    7101. Take a look at the selection in selection list panel (2 nodes)
     111. Fix all reported duplicated nodes
     121. Run validator
    813
    914==== What is the expected result?
    10 As the nodes are merge with the fix only one node should be listed in the selection list panel.
     15Nodes are merge with the fix and only one node should be listed in the selection list panel.
    1116
    1217==== What happens instead?
    13 Displayed selection in selection list panel does not change. Still both nodes.
     18Displayed selection in selection list panel does not change. Still both nodes. \\
     19Nodes are not merged.
    1420
    1521==== Please provide any additional information below. Attach a screenshot if possible.
    16 I tried to select the younger one (higher id) which is deleted and it works but deleting the node deletes the other one, so I think it is hopefully only a problem of updating the display of the selection list.
     22I tried to select the younger one (higher id) which should be deleted and it works but deleting the node deletes both, so I think ~~it is hopefully only a problem of updating the display of the selection list~~ there could be even more hidden problems.
    1723
    1824Or did I find a critical bug?