View Single Post
  #3   Spotlight this post!  
Unread 28-01-2016, 11:29
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,751
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 (navX) Library into Labview

If a vendor has LV VIs, that is almost always the ones you want to use, and adding the VIs to user.lib or other dynamically scanned folders is the general way to add them. If the vendor hasn't made VIs, then the import .net or ActiveX or dll is one way to wrap and get an initial set of VI wrappers, but they are hardly ever a nice API until you spend time to make the VIs nicer.

Greg McKaskle
Reply With Quote