Possible To Import Existing mnu to Pallete?

[lvb]

I am attempting to build an instrument driver into an VI Package (VIP) and have run into a few issues:

 

 

1. The instrument driver was mass compiled within the "\instr.lib" folder and created an error upon the package build

To work-around this, I moved the driver folder to a temporary path and re-compiled the lvlib. This seems to break the .mnu files located within the lvlib (LabVIEW issue).

 

2. Is there a way to import an existing mnu configuration into VI Package Builder? It seems tedious to re-create a pallet set that already exists.

 

 

Note: Manually copying the driver folder into the "\instr.lib" folders works great. Is there a way in a VI Package Builder to bundle and copy a set of files without modifying?

 

 

 

Thanks!

[Michael Aivaliotis]

Currently there is no mnu import tool. We are looking at ways to improve this process for people migrating old tools to VIPM. For now, you will have to re-create the palette in VIPM.

 

Also. You cannot build packages of your source code if it is beneath the LabVIEW folder. Your source code must be in a separate folder outside LabVIEW. VIPM can build the package there without problem.

 

Again, sorry for this but you will have to rebuild the palette. This is actually pretty easy with VIPM since it will auto-generate a palette for you. With some small adjustments you can get it setup in no time using the WYSIWYG interface.