03-07-2006 04:40 PM
03-07-2006 05:06 PM
02-06-2017 05:07 PM - edited 02-06-2017 05:16 PM
I can give an example as when it would be good to make an output terminal required:
When you use a common data type between multiple VIs, i.e. a LVOOP class, some VIs will modify that data type and other will just just read that data type. It would be nice to make the output data type terminal required for those VIs that modify it. This will create a broken run arrow for those cases the user forgets to wire the output back into the shift-register or cluster where the application stores it.
Some might argue that when using classes, you should always wire the output class data type to be used for in future/downstream references. However, I find that often this is not necessary and just makes it more difficult to create a clean easy to read block diagram. If that was the case, then there should always a be a broken run arrow if the output class data type was not wired.