LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
d.w.b

Bundle to automatically name Static VI Reference element as for other references

Status: New

Bundle automatically names cluster elements for some references but not to a VI.

dwb_1-1729527929738.png

4 Comments
raphschru
Active Participant

@d.w.b wrote:

Bundle automatically names cluster elements for some references but not to a VI.


Indeed, but that has nothing to do with the Bundle primitive, which simply takes the wire names.

In this case, the wire coming from the static VI reference has no name.

 

The more technically correct idea would be: "The Static VI Reference node should name its output wire the same as its label (which is normally the qualified name of the referenced VI)".

 

In your case, it should output a strictly-typed VI reference named "Editor.vi".

Then the Bundle would use the wire name as for any other wire type.

d.w.b
Member

Then it's too bad that explicitly setting the Label of the wire does not name the element. Wire Labels appear to default to blank (see Vertical Softkeys wire) and changing one has no effect on the bundle element (see "wire Label").

dwb_1-1730122075968.png

raphschru
Active Participant

I should have said "data name" instead of "wire name" (which can be confused with "wire label").

The data name and the wire label are 2 distinct things.

 

There has been an idea already to rename the data using the wire label:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-Wire-Labels-to-Dictate-Name-Inheritance-in-Bund...

 

Yamaeda
Proven Zealot

Yes, Label should be the bundled name, and it should be overridable by the Wire label.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer