LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

Save a subvi in same file as parent file

That would be usefull to elimimate all the files needed by a polymorphic VI and would also be useful in malleable VIMs where a portion of the code is needed in multiple cases but will or should never be used outside of the VIM.

4 Comments
Knight of NI

I put my polymorphic VIs inside of an LLB.  That should meet your needs.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Active Participant

I agree it's the closest that can be done with the current tools but that was not the idea. The goal was too have one file visible in the file system only. Putting things inside a llb would mean at least 2 files if i want the inside "main" file to be visible also. Also means more steps to create and also modify my scripting tools to take the llb into consideration.

 

 

Proven Zealot

Duplicate (and duplicate is declined):

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Save-polymorphic-VI-as-single-file/idi-p/1061975

 

We are not going to be implementing this.

a) The rise of source-code control systems strongly pushes back against this sort of packaging during development. LabVIEW NXG investigated and concurs with previous analysis.

b) For deployment in LabVIEW 20xx, LLBs exist and serve the role quite well. For LV NXG, deployment is done through packages that go beyond just the VIs and include the necessary support files (such as the help documents) that such a library of VIs would need.

Proven Zealot