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!
Showing results for 
Search instead for 
Did you mean: 

Create SUB-VI from selection should intelligently inherit control names

Status: New

When you select a portion of code to create a sub vi, the logic that names the contorls on the sub-vi makes some bad choices.  For example:


 before subvi.png


In the block diagram above, the selected portion of code will be used to create the sub-vi.

The resulting sub-vi front panel looks like this:


generated subvi.png 


Notice that the input control inherited the name of the control from the parent but the output did not.  Also note that the error output control inherited the name of the output from the sub-vi inside the new sub-vi, but the input error did not and ends up with the name 'error out 2'.  This of course would NEVER be the right name for this control.


It would be a lot smarter if the new sub-VI inputs would inherit their names from the inputs of the functions inside the sub-vi since that more accurately describes what they will do with those controls.  Also, I think the output indicators should inherit their names from the original destinations in the parent VI since that more accurately describes the data they will contain once the sub-vi executes.


The current behavior seems to be exactly the opposite of what a developer would want. 

Certified LabVIEW Architect
Trusted Enthusiast
Duplicate of Heuristic labels for terminals made during "Create SubVI From Selection"
Wirebird Labs: Expert Toolkits for LabVIEWDeploy, by Wirebird Labs: Expert Toolkits for LabVIEW
Active Participant

Yes, that one points to the same issue but I think my suggested solution is much better because it tries to get at the intent of the developer and is language agnostic.  Also, the description in the other entry is not correct, as it is the error input that is always labeled wrong.


Any, I have pictures in mine so people will actually read it!  😉 

Certified LabVIEW Architect