Difference between revisions of "Clones nodes"
m (trying to better explain that clone-nodes are not "one-same-node", although they give that perception) |
|||
Line 3: | Line 3: | ||
The '''Nodes Clones''' feature enables a node to become a '''clone-node''' ingroup with other ''clone-nodes'' that all ''share the same content'' (text, format, icons, etc), appearing as if they were ''one common node'' mirrored in multiple places on the map. | The '''Nodes Clones''' feature enables a node to become a '''clone-node''' ingroup with other ''clone-nodes'' that all ''share the same content'' (text, format, icons, etc), appearing as if they were ''one common node'' mirrored in multiple places on the map. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 13: | Line 8: | ||
The clone-nodes are visually undistinguishable from each-other in a map - node-A and node-B look the same because they share the ''"same-common-content"'': same text, icons, format, etc. So the clone-nodes look like as if they were ''one common node'' mirrored in multiple places on the map. | The clone-nodes are visually undistinguishable from each-other in a map - node-A and node-B look the same because they share the ''"same-common-content"'': same text, icons, format, etc. So the clone-nodes look like as if they were ''one common node'' mirrored in multiple places on the map. | ||
− | |||
NOTE: If the above seems confusing, just take clone-nodes as ''one common node'' that can be mirrored (cloned) in multiple places on the map. | NOTE: If the above seems confusing, just take clone-nodes as ''one common node'' that can be mirrored (cloned) in multiple places on the map. | ||
− | You can have as many clone-nodes as you want inside | + | You can have as many clone-nodes as you want inside one-same map (inter-map clones are not possible), and each cloned node is marked with a small-rectangle in its ancestor-connector. |
− | |||
− | |||
− | |||
− | |||
Cloned nodes were introduced in freeplane 1.5 | Cloned nodes were introduced in freeplane 1.5 | ||
Revision as of 11:43, 18 May 2016
Contents
The Nodes Clones feature enables a node to become a clone-node ingroup with other clone-nodes that all share the same content (text, format, icons, etc), appearing as if they were one common node mirrored in multiple places on the map.
This feature allows you to take a node-A and make a special-copy of it as a new node-B, so that the contents of node-A become shared (or synchronized) with the contents of the node-B. If the contents of one of these nodes is manually changed, then the contents of the other node will also be changed - because both nodes share the "same-common-content". Both node-A and node-B are called clone-nodes because they share "one-same-common-content".
The clone-nodes are visually undistinguishable from each-other in a map - node-A and node-B look the same because they share the "same-common-content": same text, icons, format, etc. So the clone-nodes look like as if they were one common node mirrored in multiple places on the map.
NOTE: If the above seems confusing, just take clone-nodes as one common node that can be mirrored (cloned) in multiple places on the map.
You can have as many clone-nodes as you want inside one-same map (inter-map clones are not possible), and each cloned node is marked with a small-rectangle in its ancestor-connector. Cloned nodes were introduced in freeplane 1.5
Please help maintain this info up-to-date - if you see an improvement please contribute to this wiki, or tell about it in this forum thread: https://sourceforge.net/p/freeplane/discussion/758437/thread/4d85148b/
How to clone a node
It is like copy/paste, only that you do Paste Clone [Ctrl-D] (instead of paste [Ctrl-V])
Quick-resume: how to clone a node
- select node to clone
- Edit/Copy/Copy [Ctrl-C]
- select destination, where to put the clone
- Edit/Paste Clone [Ctrl-D]
- Notice that cloned-nodes are marked with a small-rectangle
- Select any cloned-node, and change it
- Notice that when one clone is changed, all clones of it also change
- Select any cloned-node, right-click in it, Goto
- Notice the list of other related cloned-nodes, to where you can "Goto"
Unclone a node
If you have a cloned-node that you want to simply make it a copied node (and not a clone anymore, just a copy), then you can unclone the node.
Quick-resume: how to unclone a node
- select node to unclone
- Edit/Unclone
Subtree: how to clone a node with or without cloning its subtree
When a node is cloned, its subtree is also cloned along. However, there is an option to only clone a single node without cloning its subtree
Quick-resume: how to clone a single node without subtree
- select node to be cloned (without subtree)
- Edit/Copy/Copy node (single) [Ctrl + Shift + C]
- Notice that to clone-with-subtree we use Edit/Copy/Copy [Ctrl-C], but to clone-without-subtree we use Edit/Copy/Copy node (single) [Ctrl-Shift-C]
- select destination, where to put the clone
- Edit/Paste Clone [Ctrl-D]
- Notice that only the single node was cloned, and not its subtree
Connectors inside a cloned-subtree are cloned
- Connectors that are "inside" of a cloned-subtree are cloned
- Connecters that go "outside" of a cloned-subtree are not cloned
How to automatically apply a style to all cloned-nodes
Its possible to create a style ("MyStyle" for example) and then create a conditional-map-style that makes the "MyStyle" be applied to all cloned-nodes. This can be convenient to highligh the cloned-nodes over the normal-nodes.
The steps are ilustrated in the following image:
This was discussed in the freeplane forum thread https://sourceforge.net/p/freeplane/discussion/758437/thread/aa103640/#e2ca
All cloned-nodes share the same content (text, style, etc..). But, each freeplane node (even cloned-nodes) have an unique NODE_ID.
For more info about Scripting Api and cloned-nodes, see http://freeplane.sourceforge.net/wiki/index.php/Scripting:_API_Changes