Opened 16 years ago
Closed 11 years ago
#2952 closed enhancement (wontfix)
option to choose which node survives merging operation
| Reported by: | zorque | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | skyper |
Description (last modified by )
Hi,
it would be helpful if I had the choice to choose which node survives a merging operation an which one will be deleted. at the moment everything is transfered to the older node. To me it seems better if i.g. the first selected node remains and the other one is deleted, or vice versa.
thanx
zorque
Attachments (0)
Change History (10)
comment:1 by , 14 years ago
| Component: | unspecified → Core |
|---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
comment:4 by , 11 years ago
This is the intended behavior in order to retain the history of old objects in favor of new ones. The order of selection is already used to determine the location of the merged node. The identity (id) is handled independently.
Why do you care which of the nodes survives and which one is deleted?
follow-up: 6 comment:5 by , 11 years ago
In #10472 it seems we keep the highest id? Sounds like a bug, no?
follow-up: 7 comment:6 by , 11 years ago
follow-up: 8 comment:7 by , 11 years ago
Replying to bastiK:
Replying to Don-vip:
In #10472 it seems we keep the highest id? Sounds like a bug, no?
skyper should double check if this can be reproduced, it's supposed to be always the lowest positive id.
Do not really remember the case and even might have swapped digits. Anyway, cannot reproduce atm.
Though, we have a different behaviour when
- merging by draging while holding
Ctrl - merging using merge function
The first gives different results depending on selection while the second one is selection independent.
comment:8 by , 11 years ago
Replying to skyper:
Though, we have a different behaviour when
- merging by draging while holding
Ctrl- merging using merge function
The first gives different results depending on selection while the second one is selection independent.
Thanks for pointing this out, we should probably fix the Ctrl merging then.
comment:9 by , 11 years ago
Hmm, The Ctrl-Merging is an "Merge this to that". As far as I remember this was done on purpose and also solved all these issues when someone really wanted a special node to remain. I don't think this should be fixed. At least before changing it all the relevant old tickets should be read.
I think this bug is more or less a WONTFIX to me.
comment:10 by , 11 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Ticket #10472 has been marked as a duplicate of this ticket.