Modify ↓

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#3798 closed defect (fixed)

[PATCH] Merge nodes tool - respect selection order

Reported by: bastiK Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: Merge nodes Cc:

Description

When using the merge tool (M) you cannot decide what node is going to be the target node for merging.

With this patch it is always the node selected last.

Attachments (1)

merge-order.patch​ (3.9 KB ) - added by bastiK 15 years ago.

Download all attachments as: .zip

Change History (5)

by bastiK, 15 years ago

Attachment: merge-order.patch​ added

comment:1 by stoecker, 15 years ago

Hmm, I would say merging to the first one is better. I think this is a more common workflow to first select the target and then all the sources.

comment:2 by bastiK, 15 years ago

My picture is that everything gets sucked into the last position of the mouse curser.

But I don't really care, as long as it is consistent.

comment:3 by Gubaer, 15 years ago

Resolution: → fixed
Status: new → closed

(In [2341]) applied #3798: patch by bastiK: Merge nodes tool - respect selection order

comment:4 by Gubaer, 15 years ago

I'v applied bastiK's patch and didn't change the order. Personally, I also prefer to merge to the last selected node.

Should we make this configurable?

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. Next status will be 'reopened'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.