From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
07-02-2014 08:22 PM
@nperhach wrote:
The files does create a *.mnu with items the write palette.vi has to take an empty cluster of items any way before it can bundle the items like in the create palette.vi example so was giving what zealot said a shot. That is true everyone would have the deployment system. Trying to make an application because I was told to, if there is not away I will settle with distributing the VI.
Trust me on this. Use VI Package Manager. I gave the link earlier. It actually comes with LabVIEW in the last few versions. With the community verion (free) you can create a package of VIs and a palette for them and then distribute the package. Then your other users just need to use VIPM to install the package to whichever version of LabVIEW they want. Yes, VIPM allows the installation of packages on a per LabVIEW install basis. JKI has spent many years working on it and it just keeps getting better. And they already did everything you are trying to do.
07-03-2014 11:46 AM
Thansk for the link. The VIPM looks like a good tool for distributing VIs and would allow the VIs to be used in any version of LabVIEW. However, for what I am trying to accomplish I need the process automated for continuous integration. Does VIPM have a command line interface?
07-03-2014 12:32 PM
@nperhach wrote:
Thansk for the link. The VIPM looks like a good tool for distributing VIs and would allow the VIs to be used in any version of LabVIEW. However, for what I am trying to accomplish I need the process automated for continuous integration. Does VIPM have a command line interface?
Let me see if I'm tracking you. Your requirements are:
You do not need an application for that! You just need to build you mnu the right way!
Build and deploy a sub-palatte linked to the directory containing the deployed items. When new items appear in that directory they show up on the pallet linked to the directory! (If you load palettes during launch you need to restart LabVIEW)
Untitled 36 was just added to my reuse folder just for you It'll go away when I delete the blank vi
07-03-2014 01:06 PM
When I originally started making the palette I was using the synchronus with directory, but I thought it might be a good idea to remove that because if there are other files or folders it would create an empty slot in the palette. I may try putting that back on so users can add VIs to the subpalette without having to run my application again. The reason I need to either distribute an application or a vi that converts the VIs to a mnu file is because if I build a mnu file and then distribute it with the VIs, it looses the links to them and the palette has a '?' in the VIs place. Also, I want the application because I do not want the user to have to build the palette manually instead they can just run the application.
07-03-2014 01:17 PM
@nperhach wrote:
When I originally started making the palette I was using the synchronus with directory, but I thought it might be a good idea to remove that because if there are other files or folders it would create an empty slot in the palette. I may try putting that back on so users can add VIs to the subpalette without having to run my application again. The reason I need to either distribute an application or a vi that converts the VIs to a mnu file is because if I build a mnu file and then distribute it with the VIs, it looses the links to them and the palette has a '?' in the VIs place. Also, I want the application because I do not want the user to have to build the palette manually instead they can just run the application.
Hide Synch item
07-03-2014 02:29 PM
07-03-2014 03:29 PM
The .mnu file is installed in the user.lib folder so the palette is placed in the user libraries subpalette or in menus\categories for its own palette. I am currently using perforce as my source repository.
07-03-2014 03:37 PM
07-03-2014 03:45 PM
I do not think I need something else. The vi is just for purposes of automating creating a palette for VIs from a folder on perforce. And I wanted to have the vi as an exe for distributing purposes, but I get an error since write palettevi is not supported by the run time engine.
07-03-2014 03:58 PM