Modify ↓
Opened 17 years ago
Closed 17 years ago
#1582 closed enhancement (wontfix)
[PATCH] Second MergeNodes Action to merge onto the other node
| Reported by: | Henry Loenwind | Owned by: | framm |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
Merge Nodes merges on the "oldest" of the selected nodes. This patch adds a new MergeNodes2Action, that merges on the "newest" of the selected nodes.
It's not the best way to select on which node to merge, but it's better than nothing. Having these two actions, the user can merge onto every node. He might have to select the nodes pair by pair and try which action is the correct one. Not the nicest thing, but better than to select from a list of node IDs. Someone might want to code a graphical selector, but that's not my field of expertise.
This patch includes:
- New file MergeNodes2Action.java
- Patch to MergeNodesAction.java to allow subclassing
- Patch to MainMenu.java to include new action in Tools menu.
Note: If someone knows of a free key to the shortcut, feel free to add it.
Attachments (3)
Change History (5)
by , 17 years ago
| Attachment: | MergeNodes2Action.java added |
|---|
by , 17 years ago
| Attachment: | MergeNodesAction.diff added |
|---|
by , 17 years ago
| Attachment: | MainMenu2.diff added |
|---|
comment:1 by , 17 years ago
Note:
See TracTickets
for help on using tickets.
I do not like that solution. It produces two tools for one problem and it is not really something users will find intuitive.
If you want to improve it, then please make a solution which always merges onto the first select node. That would possibly be a useful solution.
Anyway I'm against two similar tools for one task.