LabVIEW
Get the control references from Dynamic Event Registration refnum
Solved!
@1984 wrote:
I typedef'd it because more than one VI will use the input (not at the same time of course). I agree that using a class is also an option (maybe even a better one), but right now a typedef'd cluster looks good enough to me and more within my comfort zone.
Sure, suit yourself. Nothing wrong with it, but I tend to find it a waste of time iff used only once or twice. Obviously a type def can safe lots of time.
Search LabVIEW like a graph! 
@pincpanter wrote:
Nearly 100% of the times I overlooked typedefining a cluster or an enum I had to do it later.
But I'm not currently in the OO business.
I had that at first (let's say the first 15 years 😊), but now I hardly ever need to change to a type def afterwards.
There isn't a real downside, except when your code gets really big. If you have 180 type defs that are just used to bundle an input, to me the type defs gets less practical than they are useful. Also, those clusters tend to be reused, and this could mean more tight coupling than needed. This is also a 'big project' problem, that you can often get away with.
There's no type def law nor a type def police. Just saying that if you don't really like to make them type defs, there are times when it's fine to not make them. If you do like it, it's fine by me, and it isn't even up to me.
@pincpanter wrote:
Nearly 100% of the times I overlooked typedefining a cluster or an enum I had to do it later.
But I'm not currently in the OO business.
This must be common enough that, starting with LV 2018, the "control" selection when you right-click on a folder and select "new" in your project has been replaced with "typdef".
