Propagating Inputs

Hello,

I find the Propagate Outputs feature to be extremely useful. It would be beneficial to allow function group inputs to be propagated as well. I tend to use nested function groups quite often to keep my programs clean and easy to follow, and as a result I will typically have the same function group input repeated in order to pass information along. This feature would not be useful if that data being passed through each function group was being used in each one, but I often find myself passing data through function groups without using it in any of the intermediate function groups. For these cases, being able to propagate inputs would be extremely helpful.

The below example should help clarify what I mean. This is a part of an external function I am creating to control a CANOpen device. To make this external function as generic as possible, I have created this COB-ID generator module that will combine a user defined Node ID with a predefined TPDO/RPDO. This nested function group is the only part of the program that interacts with the FC NODE ID & NFLS NODE ID function group inputs. These FGIs would not need to be in place if propagating inputs was implemented. The middle picture shows what is inside the COB-ID GENERATOR function group, and the last picture shows the main external function group.