Leaderboard

This is what LavaG is here for. No-one has even seen this new structure yet and we are already trying to figure out how we can abuse it

"Abuse" is such a strong term. I prefer "innovative use", or "thinking outside the box"

Not quite. So the VI macro works like the XNode (cause it is) where an input can have the ability to become any data type, then the type propagation within the VI will go through all the primitives inside, or polymorphic types, or whatever just like it does when you change the type on a wire in a normal VI. The output changes based on the input, in almost all situations, the reverse is not true. When you wire the output of an XNode the inputs don't change. The only exception I know of is with a few XNodes like my Variant Repository, which will look up stream when you wire an output, and then attempt to change the output to be the type that it is wired to. Another exception to this is the variant to data, where in some rare cases it will change the output based on what is wired to it, and the Type input can be left unwired. I would not expect this new structure to work this way. I suspect it just looks at the inputs and sees which cases cause no broken wires, then changes the outputs as needed. BTW can't wait for 2016 now, along with a few other beta features that will finally be given the attention they need.

So there's an off-list thrust in breathing some life back into this thread. If you haven't watched the presentation, and are interested in making error handling in LabVIEW better, please do so and post your thoughts. I'd like to come up with a feature list and add a timeline to it.