View Single Post
  #3   Spotlight this post!  
Unread 05-03-2016, 17:14
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Importing Nav-x mxp library

The navX actually ships as a zip, so it will be a folder of VIs and Ctls and a file called navX_v2.lvlib. If you do as Alan and said and drag the folder into your project folder, that will allow you to put it into source code control if you are using it.

By the way, drag and dropping the .lvlib file from the file explorer into the LV project explorer under the target will also work. Done this way, you can just toggle open the .lvlib in the project and you can drag the VIs to your diagrams.

If you want the VIs to be in the palettes instead, you can put the folder into user.lib folder under the LabVIEW folder. It will get a palette, but I believe an autogenerated one.

Greg McKaskle
Reply With Quote