Provide a better way to implement a polymorphic VI

[DanyAllard]

Let’s take the Value Changed from OpenG, This polymorphic as 30+ VIs to support all data type and array size up to 2D. But basically it’s the same VI for all data type.

 I think it could be a “.vip” and when you define the connector pane you select constraint of the possible data type that can be accepted.

[bean123]

It probably should say "In Progress".  With 2016 a new unofficial structure was introduced called a Type Enabled Structure.  See conversation here:

https://lavag.org/topic/19163-vi-macros/?do=findComment&comment=119393

[Tomi_Maila]

I posted a related idea on type parameters and parametrized which would allow extending the reusable nature of type independence from VIs to custom types (classes). 

Type Parameters & Parametrized Generic Types

[WG-]

Good to hear that this is finally getting some priority.

[Darren]

Available in LabVIEW 2017. Use Malleable VIs (.vim files) to define a generic implementation for a single subVI that will adapt to multiple wired input data types.

[DanyAllard]

Great addition to LabVIEW.

Thank you to have completed this idea