cut-and-paste of "use comp"s together with their "comp start"s breaks connection

[rozek]

After moving "use comp" nodes and their associated "comp start" nodes onto a new sheet/tab with cut-and-paste (using the internal clipboard for nodes) the connection between these two gets lost and has to be re-done. Forgetting to do so stops a flow at the first "use comp" node.

I just moved flows with many "use comp" nodes from one tab into another one and had to fix many lost associations...

[ollixx]

You say you moved both run and start nodes? Is that by intention? A copy of a start node creates a new component und thus you have to wire any run nodes to use it.
A copy of a run node should of course work, as it keeps the reference to the original flow, i. e. Start node. I will check that out.
What would be your expectation, when you copy both run node and the definition nodes?

[rozek]

Please note, that I have "cut" the mentioned notes into the clipboard, not "copied" - that seems important.

The idea was to "move"(!) a complete flow from one tab into another in order to have more room on the workspace for improvement.

Therefore, I removed all nodes with their wires from one tab and inserted everything into another one - and had to reassociate all "use comp"s with their "comp start"s again...

[rozek]

Important!

I found an astonishing workaround: if I "export" the flows to be moved into a text editor, remove them from the workspace (optionally followed by a deployment), switch to another tab and reimport the flows there (and deploy again), the "comp" nodes keep their associations and everything works like a charm!

This workaround helps a lot - and, perhaps, it even helps you when finding the underlying reason for the bug.

[ollixx]

Hi Andreas, thanks for your feedback.
If never cared to look into the difference between cut/paste and export/import. Now I did:

• cut/paste always creates new nodes with new node IDs. NR is of course not able to understand, that the reference from RUN to START node has to be changed as well, so the flow is broken.
• export/import is a little more "intelligent", as it reuses the same IDs from the export, if those are not already in the system. That means, if you export, remove the nodes (and thus the IDs) and reimport them, the IDs will be the same. The RUN refers to an existing START and it works.

To make cut/paste or even copy/paste work, the nodes would have to use another Identifier for the flow, that is not depending on the node IDs. When I think about Cut/Paste, it's not such a big deal.
Copy/paste would need to recognize duplicate Identifiers and correct them after the paste. Not sure, if that is really possible
Ii will take a look at that

[ollixx]

I merged your PR, thanks for your effort!
But I had to move that a bit down, as it should not be the first thing to mention in the README. I also condensed the text a little.
Thanks again for your feedback!