LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Create subVI Control from Reference Name Bug

If you connect N references to a sequence structure and create a subVI from this structure, the first N-1 controls will have the name of the original control (desired), but the last one will not. It will have the name of the generic type of the control this reference is pointing to. Of course, if N = 1, that means that the created control will have the generic name.

 

Illustration:

 

ScreenHunter_001.jpg

 

In the diagram above, subVI 1 has been created from a sequence to which a reference to "Numeric Control" was connected. Here is the FP of that subVI, as created by LV:

 

ScreenHunter_002.jpg

 

subVI 2 was created from a sequence to which both references were connected. Here is the FP of that subVI:

 

ScreenHunter_003.jpg

 

This does not seem to depend on the type of the control. If I add a graph:

 

ScreenHunter_001.jpg

 

the created subVI looks like this:

 

ScreenHunter_002.jpg

 

Message 1 of 3
(2,595 Views)

Kind of an extension of this bug, but not exactly the same. Might be due to the same cause though

If you create a subVI incorporating Property Nodes (not recommended in general for performance reasons, but not a killer either), the subVI will obviously have references to the corresponding controls as controls and references to the controls will appear in the calling VI:

 

Before:

 

ScreenHunter_002.jpg

 

After:

 

ScreenHunter_003.jpg

 

(it never ceases to amaze me how bad the cleanup/auto-routing algorithm developed by NI is 🙂

 

Here is the corresponding FP of the created subVI:

 

ScreenHunter_004.jpg

 

This time, never mind the names of the original controls, they will be ignored, no matter how many different controls there is.

 

(I am not even mentioning the well-known feature that if instead of enclosing the property nodes you just enclose the wires coming from the "Value" node, the subVI's controls will read "Value, Value2", etc, where the type of the "Value" controls will in general have absolutely nothing in common).

 

 

Message 2 of 3
(2,589 Views)

Hi Alex,

 

I have validated this behavior, and have reported it to R&D (# 352158) for further investigation. It appears at this point that this issue with refnum names only affects 2011 and 2011 SP1. Thanks for the feedback!

Tom L.
Message 3 of 3
(2,568 Views)