Showing results for 
Search instead for 
Did you mean: 

Type Specialization Structure in 2017

In the NI week presentation on malleable VIs there was a reference to to a "Type Specialization Structure". Do you have to do anything to get access to that structure? I can't find it anywhere

0 Kudos
Message 1 of 5

It's not on function palette.

You have to open an example, and copy from the diagram.



George Zou
0 Kudos
Message 2 of 5

The Type Specialization Structure was not officially released.  Apparently there were a few bugs and/or missing functionality they wanted before making it widely available.

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 5

I made a really simple right-click plugin which should allow you to replace a Diagram/Conditional Disable Structure with the Type Specialization Structure. If you add the attached .llb to <LabVIEW 2017>\resource\plugins\PopupMenus\edit time panel and diagram the option should show up right below the options to replace with conditinal/diagram disable structure.

Matt J | National Instruments | CLA
Message 4 of 5

I believe the issue R&D found with the structure was in developing for it, and I heard someone else mention how it doesn't always work with classes like you'd expect.  I'd often find that when developing code, a type wouldn't always do what it needed to, and I'd need to force a recompile, or delete things and rewire to get the VIM to do what I wanted.  But after it was good and working the structure never gave me any stability issues.  


That and I think something was mentioned about it might not work as expected with classes at the moment.  This and the lack of documentation is a good reason to avoid using it, but if you do use it, it sounds stable.  I mean NI themselves are using it so the technology itself likely isn't the problem, but edge cases where it might not work right, or might be difficult in getting the compiler to do what you want.  When it is official (2018 maybe?) we will likely see it on the palette, and Jacobson's tool shouldn't be needed.

0 Kudos
Message 5 of 5