Back Propagation of 'Create User Event' Datatype

[McQuillan]

I use a lot of user events and often define the user event references in a typedef cluster before actually writing the create/generate/destroy code. It would be really helpful if the Create User Event primitive would change its input datatype based on the output (i.e back propagate the datatype), much like the Variant To Data primitive.

[McQuillan]

^The input would still be 'Required' and require a label. But it would mean we can just right-click and create a constant, instead of searching for the datatype in the project/quickdrop (if you can remember the name).

When I can't remember the data type at all, I sometimes revert to using the Generate User Event function to get the datatype.

[Intaris]

Yup. No more to be said.

[tst]

Seems like a decent job for a right click/QD shortcut (either creating the typedef constant from the user event ref if you really do a have a user event refnum or a more complex process if what you have is just a typedef for the event data).

[AristosQueue (NI)]

Lots of back propagation magic is possible in LabVIEW. Gets my vote.