LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Assigning VI as top-level within a folder in a Project Construct

I converted an LLB to a folder of VIs, and this folder resides within a project under 'My Computer'.  The folder has hundreds of VIs now.  I want to assign a VI as top-level so that it 'stands out' from the others, like you could do in the LLB construct.  The only thing I could think of doing was just moving it within the folder to make it the first VI.  Any other way to specifically assign a VI as top-level within a folder?

Thanks,

Don
0 Kudos
Message 1 of 5
(2,804 Views)
Hi Don,

you can right click on the project and select 'new->folder' and move all VI's into (note this will not move the files on disk)
The drag your topvi's out of the folder into the root of the project

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 5
(2,801 Views)
Assigning "toplevel" status is one of the (very) few useful perks of the old LLBs. There is no such mechanism available in windows explorer. ('don't know about MAC and linux).
 
I agree it would be nice if such a feature would exist such that all toplevel VIs in a folder stand out somehow, e.g. with a different icon. (This could be automatic, e.g. all VIs without any connector pane connections, or manual by a VI properties designation). I don't know how easy that would be to implement but you can always go to the product suggestion center and request it. 😉
 
Of course the LabVIEW project allows you to structure a hierarchy even if all VIs used reside in the same folder. That won't help you of course if you inherit a folder with hundreds of assorted old VIs. 😞
 
Some casual testing shows that if you import an entire llb into a project (with "add folder...") it will dump everything in the same place, irrespective of toplevel status.
 
(Similar problems arise if somebody attaches a zip file with some problem here and it contains 20 oddly named VIs and we have to guess what the toplevel possibly could be.)
0 Kudos
Message 3 of 5
(2,794 Views)

Right, the points you raised are all the reasons why I brought this up.

What I have done (even before the first reply was sent on this topic) was to just pull the top level VI out of the virtual folder (within the project window) and have it stand by itself.

I would expect someone from NI would monitor this forum and consider a way to specifically demarcate a top-level VI within the project construct (but if you think this is a bad assumption, I could submit it as a suggestion for future release).

Sincerely,

 

Don

0 Kudos
Message 4 of 5
(2,767 Views)
It would be a nice feature of the import function.

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 5 of 5
(2,759 Views)