This is a blatant copy of an idea from 2021, but it came up in a recent customer meeting.
While I agree that modifying event arguments is possible to do manually, can we take another look at automating that?
Right now if an argument is added to / removed from the typedef, it requires the developer to manually perform a series of (scriptable) actions:
- Open the public event VI
- Create a new control or indicator OR remove existing
- Expand the bundle/unbundle, and wire it in OR collapse the bundle/unbundle to get rid of the deleted argument(s)
- Wire the new item to the conpane and set it to Required (in the case of a control)
- Update the EHL case to make sure the cluster is properly bundled (can be checked by the validator)
- Take care of updating the Tester
So here we have a multi-step process where things could be easily forgotten. Order of operations matters. The steps are well defined. The activity is dull. It feels like a good candidate for automation.
Accepted. Added to backlog for v8.