Modify

Opened 11 years ago

Closed 6 years ago

#2447 closed enhancement (fixed)

Unnessary changes of a target node by dragging another node onto it

Reported by: fidoez Owned by: team
Priority: minor Milestone:
Component: Core Version: tested
Keywords: drag node Cc:

Description

If I drag a node (end of a way) onto an existing node (here called target node) JOSM markes the target node as modified. This is unnessary and causes redundant database entries.
The deletion of the dragged node and the modifcation of the way containing the dragged node is correct.

Attachments (0)

Change History (4)

comment:1 Changed 11 years ago by plaicy

Owner: changed from team to fidoez
Status: newneedinfo

I can not reproduce this in r1985.

  1. Download osm data
  2. Save data to file
  3. Go to the end of an existing way A
  4. add another way B (two nodes) near the existing way
  5. drag one end of B on the end of A
  6. Save data to new file
  7. Try to upload: JOSM reports no changed node

I also compare files in 1 and 6. There are only two nodes and a way added, no existing node is changed.

comment:2 Changed 11 years ago by fidoez

Owner: changed from fidoez to team
Status: needinfonew

Sorry, I didn't mention that you have to press CTRL to "Merge with nearest node" at your step 5, i.e. merge the end of B with the end of A.
The Result should be: one node and one way added - nothing else

comment:3 Changed 10 years ago by Gubaer

Priority: majorminor
Type: defectenhancement

This is hardly a major issue. Everything works fine. There's only a small potential to improve efficiency. Changing into a minor enhancement.

comment:4 Changed 6 years ago by Don-vip

Resolution: fixed
Status: newclosed

In 6202/josm:

fix #2447 - Unnessary changes of a target node by dragging another node onto it

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.