Modify

Opened 2 months ago

Last modified 8 weeks ago

#17866 reopened defect

Merging nodes: youngest instead of oldest id and history kept

Reported by: skyper Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: template_report merge node history Cc:

Description (last modified by skyper)

What steps will reproduce the problem?

  1. Have an node and another node with higher id than the first one.(568979540, 3825090301)
  2. select them (order does not matter)
  3. merge them with menu function or keyboard shortcut 'm'

What is the expected result?

Lowest Id and history of the oldest node is used/preserved.

What happens instead?

Id and history of the younger node is used.

Please provide any additional information below. Attach a screenshot if possible.

Thought the order of selection did matter some time ago.
Strange, it seems to happen only on some sessions.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-06-24 20:49:39 +0200 (Mon, 24 Jun 2019)
Build-Date:2019-06-25 01:30:58
Revision:15195
Relative:URL: ^/trunk

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.

Attachments (1)

josm_17866_example.osm (3.7 KB) - added by skyper 8 weeks ago.
example file

Download all attachments as: .zip

Change History (5)

comment:1 Changed 2 months ago by skyper

Resolution: invalid
Status: newclosed

Strange, now I can not reproduce. Damn, should have kept the example.

comment:2 Changed 2 months ago by skyper

Description: modified (diff)
Resolution: invalid
Status: closedreopened
Summary: Merging nodes: youngest instead of oldest id and history keptMerging undeleted node: youngest instead of oldest id and history kept

Forgot about that I had undeleted (edited) the older node.

Need to find an example, again.

comment:3 Changed 8 weeks ago by skyper

Description: modified (diff)
Summary: Merging undeleted node: youngest instead of oldest id and history keptMerging nodes: youngest instead of oldest id and history kept

No undelete needed.

I add an example file.

Changed 8 weeks ago by skyper

Attachment: josm_17866_example.osm added

example file

comment:4 in reply to:  description Changed 8 weeks ago by skyper

Replying to skyper:

Strange, it seems to happen only on some sessions.

Some thing strange is going on:
It seems to work as expected for all nodes except the one with tags where always the id of the untagged node is used.

Had this problem with two tagged nodes as well, today. Quite annoying to watch the ids on every merge and once it happens you need to construct around with temporary objects.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as reopened The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to skyper
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket

Add Comment


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

 
Note: See TracTickets for help on using tickets.