LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
jgcode

Allow VITs and CTTs to Behave Correctly As Merge VIs

Status: New

Currently if you drop a Merge VI containing VITs or CTTs from the palette onto you BD it is dropped as the Template not an Instance of the Template.

Obviously we want the latter.

 

It would be nice if this was handled by LabVIEW so that we can centralize an API with Templates through the palette.

 

22611iAB7F805B911B7AC0

 

This is related to this Idea.

 

See here and here for side chatter (and the original Idea).

 

Additionally, to top it off, this will be great when the outstanding CAR to fix up a bug with FP Object positions in completed 🙂

 

 

Certified LabVIEW Architect * LabVIEW Champion
3 Comments
shew82
Member

Now that's a feature that would be really helpful in reuse libraries / add-ons! 🙂

 

 

...although, I personally consider the current behavior to be more of a bug than a missing feature...

shew82
Member

Although... thinking about your specific wording some more... I think this should work for regular palette VIT/CTTs as well as merge VITs -> that way you could get new VIs with proper FP properties, connector panes, etc as well.

jgcode
Active Participant

Hi Shaun

 

Yes I am interested in this - please continue go into more detail.

 

Are you thinking this Workflow/Use-Case too:

Label/Mark a VI as "Template" (just like Place VI Contents) in the Palettes

When you drop the VI on the BD it creates a new instance of it in memory (completely separate from the Palette VI)

All FP properties, colors, CP etc... are persistent

Any SubVIs or Controls that are Templates get instantiated as well. 

 

Cheers

-JG

Certified LabVIEW Architect * LabVIEW Champion