User | Kudos |
---|---|
4 | |
4 | |
4 | |
2 | |
2 |
If you have an event that contains a cluster typedef, then the event structure automatically unbundles the data:
I generally want to work with the entire typdef though. Why not expose the entire typdef to improve code maintainability?
(No one wants to re-bundle that data just to send it to a subVI or new event...and then risk losing data when a new property is added later. Workarounds include adding a typdef of a typdef, or going class-based...but that overhead/creativity shouldn't be necessary.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.