Suppose we have this setup:
node 1
node 2 contains node 3, which in turn contains a clone of node 1
please see picture "before_copy_cut.png" I attached below
now if we copy or cut node 3 and paste it into node "Test Map"
expected result: node 3 (after copy or cut) still contains the clone of node 1
actual result: node 3 (after copy or cut) contains a copy of node 1
please see picture "after_copy_cut.png" I attached below
This weird behaviour (or bug) caused a huge problem in one of my big maps. In the map, I have many clones, and in the past, I often rearranged the nodes by cutting them to other nodes.
Yesterday I got a panick attack when I realized that one of the clones suddenly turned into a normal node out of the blue. After several hours trying to figure out why, I detected the above mentioned bug.
After knowing the bug, I realized that I have quite a few other clones which also got turned into normal nodes.
This led to my map now in a messy state when many updates / modifications which I intended for one single node, but now scattering through various places of the map, inside copies of that node (which should be it's clones instead)
You are right, at the moment you copy or cut a node, the copied content loose their connection to the non copied part of the map. And your post it is the first time it is recognized as a problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it is a problem because in my example above, if instead of cutting, I moved node 3 by selecting it and dragging it to node "Test Map", then node 1 (the child of node 3) would not lose it cloning property.
In my point of view, cutting and then pasting a node to another location should have the same effect as dragging it to that location. In other apps, these actions are both called "moving".
Moreover, in large maps, it is impossible to drag a node to another, faraway location, so cutting is the only option to move it to the that location.
Last edit: Robertonisola 2020-10-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Roberto,
I did a little Add On for moving nodes from distant locations in a map. Maybe it can be useful for you because it moves the nodes, it doesn't cut and paste them.
Isn't it possible to create a pop up that shows up when a clone node is cut or copied, warning that the clone connection will be lost? This warning would be really convenient to me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Suppose we have this setup:
node 1
node 2 contains node 3, which in turn contains a clone of node 1
please see picture "before_copy_cut.png" I attached below
now if we copy or cut node 3 and paste it into node "Test Map"
expected result: node 3 (after copy or cut) still contains the clone of node 1
actual result: node 3 (after copy or cut) contains a copy of node 1
please see picture "after_copy_cut.png" I attached below
This weird behaviour (or bug) caused a huge problem in one of my big maps. In the map, I have many clones, and in the past, I often rearranged the nodes by cutting them to other nodes.
Yesterday I got a panick attack when I realized that one of the clones suddenly turned into a normal node out of the blue. After several hours trying to figure out why, I detected the above mentioned bug.
After knowing the bug, I realized that I have quite a few other clones which also got turned into normal nodes.
This led to my map now in a messy state when many updates / modifications which I intended for one single node, but now scattering through various places of the map, inside copies of that node (which should be it's clones instead)
You are right, at the moment you copy or cut a node, the copied content loose their connection to the non copied part of the map. And your post it is the first time it is recognized as a problem.
@dpolivaev Thank you for your response.
I think it is a problem because in my example above, if instead of cutting, I moved node 3 by selecting it and dragging it to node "Test Map", then node 1 (the child of node 3) would not lose it cloning property.
In my point of view, cutting and then pasting a node to another location should have the same effect as dragging it to that location. In other apps, these actions are both called "moving".
Moreover, in large maps, it is impossible to drag a node to another, faraway location, so cutting is the only option to move it to the that location.
Last edit: Robertonisola 2020-10-09
Yes sure it is not optimal. I am going to think about implementing it in another way, but it is a big change.
@dpolivaev thank you very much
Hi Roberto,
I did a little Add On for moving nodes from distant locations in a map. Maybe it can be useful for you because it moves the nodes, it doesn't cut and paste them.
more info in this thread: https://sourceforge.net/p/freeplane/discussion/758437/thread/501b4bfaf3/
hope it helps,
edo
@Edo thank you, I will give the add-on a try
If you want only to move nodes inside the same map, combintation "Copy" and "Move" should work as you would expect it.
wow!! it was there and I never noticed!! Thanks
Isn't it possible to create a pop up that shows up when a clone node is cut or copied, warning that the clone connection will be lost? This warning would be really convenient to me.