Variables declaration in Nodes
Wouldn't it be smart to simply make all variables available locally within the node macro automatically WITHOUT need to use NENG.GETINPUT() assuming PORT ID to be the variable name? Similar approach as in macros run for manager getting VARDEF variables. And even use variable definitions more in tabular format and not as it's today.
radovan.gasparovic@ulstein.com
shared this idea
-
AdminLari Haapaniemi
(Admin, NAPA)
commented
Thank you for your suggestion Radovan!
That is a very good idea, and it also addressed an issue we are aware of.
The neng.getinput in its current form will not be the final solution, and we are still considering whether:a) We make this statement appear automatically when you have a port.
b) Make the node port ID:s be variables automatically as you suggested.
C) Make it so that when you pass a node as a parameter, you could derive the ports directly from it (e.g. node.PORTROOM).One thing we want to ensure is that you know that the variable you have is coming from the node port, but the exact way this is defined is still something we are iterating on :)
- Lari