Provide Access to Full Event Data in Event Structures

[_carl]

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.)

[DrK.Jimenez-Marquez]

That is true!! I usually create another cluster level to get my complete typeDef in the event structure.

[AristosQueue (NI)]

I flagged this for the R&D team and added my personal kudos to the idea. I see the utility. And, I admit, sometimes I do use a cluster for my event data and have often wanted to receive the data as a coherent cluster. But, you know, if you use a class instead of a cluster for the event data, it stays coherent. Just sayin'.

Yours truly,

    the person who created LV classes and may be a bit biased about their use

🙂

[tst]

Duplicate, but let's vote for it anyway:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-Dynamically-Registered-User-Events-to-preserve-...

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Enable-selecting-top-level-cluster-in-event-data-in-e...