custom palette for vi's not under LabVIEW

[chucky]

i've created a very nice custom palette for our vi's. i've created dir.mnu files for each directory. everything is ok if the user installs the vi's under instr.lib.

however, our installer has the option of installing them some place. if the the vi's/mnu files are not installed under the LabVIEW directories, our vi's don't show up on the palette.

is there any way of telling LabVIEW where these files are so they show up?

[Mark_Yedinak]

Not that I am aware of. However if someone does give you an answer I would love to find out. This would be a nice feature to have.

[TCPlomp]

One way would be to have a post-install VI with the following code:

1. Get the installed directory some way
2. Create a .mnu file that only has a subpalette that links to the main .mnu file using the new palette api
3. Update the palette views

Ton

[Mark_Yedinak]

Actually you could use JKI's Package Manager as well. That will install the packages under the NI directory tree. You will also get the benefit of all the other nice features that VIPM has.

[TCPlomp]

But you will lose the possibility to install in a custom location.

Ton

[Mark_Yedinak]

---

TCPlomp wrote:

But you will lose the possibility to install in a custom location.

Ton

---

This is true. However what JKI Package Manager will do for you is to automate and manage the process of adding the VIs to the LabVIEW directories. The source code itself can be saved in an external source code control system and the development can take in wahtever directory you would like. The deployed versions/packages would be added to the NI directories. Is there a particular reason the files should be stored in a custom directory?