ForEach Node has no run function

[Gregor Hofer]

The forEach node had no run function and did therefore not run properly. I fixed it in my fork 41c5c03

[Jens Luebben]

Are you sure that is needed?
The 'ForEach' Node is almost fully implemented in the 'ForLoop' Node and the 'ForEach' Node worked as expected.
To recycle as much of the Node's code as possible I made the 'ForLoop' Node abstract and reused part of its implementation for the 'ForEachAtomPair' Node. Admittedly not the cleanest solution but I was in a hurry. :)

[Gregor Hofer]

I think, a simple, non-specific for-each-node is not only handy but important for batch file operations. Here is a quick example:

[Jens Luebben]

I will re-implement the ForLoop class and its children to make the intended design clearer/cleaner.

[Gregor Hofer]

I'm not sure if it's a bug or my sloppy re-implementation of the ForEach node but the second ForEach does not trigger the first.
Edit:
I just checked the console output, the last node run was the ReadAtoms node, it seems to me that the ForEach node does not like to be executed a second time.

[Jens Luebben]

ForLoops did not consider that the TRIGGER input is optional. 9a69932 should fix that.