12-08-2022 04:14 PM
I recently installed a Keysight instrument library to the instr.lib folder. Opened up LabVIEW and there it is in all its glory, a bunch of VIs to operate a Keysight instrument. But there were some implementation techniques I didn't necessarily agree with, so I added a couple VIs to (imo) do it better. Added them to the project and their respective folder locations, yet they do not appear in the Block Diagram LabVIEW menu. Is there something I have to do to the .mnu files in order for them to be visible? Looking at them via txt, it appears to be mostly gibberish. So not a simple addition. If this is the way, is there a white paper on this? If it is not, how does one do this?
(Also, I am aware of the issue of these VIs only being available to me until distributed properly to team)
Solved! Go to Solution.
12-08-2022 04:26 PM
From toolbar => Tools => Advanced => Edit Palette Set...
You can add your VI to the palette, LabVIEW will update the .mnu when you save.
12-09-2022 02:38 AM
a) It's suggested to create your own folder under Instrument I/O and put all VIs there
b) Should you consider to deliver this package to others (i. e. customers), then take the folder "as is", including the all the *.mnu in subfolders and either zip and provide or create a package with a package manager.
c) Should you consider to also deliver a help file in the form like LV does, every VI can contain a short description that will appear in the small help window, plus you can place a keyword. The keyword is used to open direct help pages in compatible file types (CHM, HLP). The keyword would create the blue link you sometimes find in the small help window. When clicking it would open the assigned help file which you also must link in every VI you are going to offer help for.
12-09-2022 10:05 AM
@zou wrote:
From toolbar => Tools => Advanced => Edit Palette Set...
You can add your VI to the palette, LabVIEW will update the .mnu when you save.
That did the trick, thank you