View Single Post
  #2   Spotlight this post!  
Unread 28-01-2010, 07:52
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: Error: This VI claims to be part of a library

Like most computer error, it makes perfect sense once you know what it means.

Libraries provide namespace and scoping to VIs. You don't have to use them to use LV, but WPILib is making use of them. Once you've defined a library, the VIs are owned and managed by the library, and will complain like this if you attempt to rip them out and use the file away from its library. When you made a copy, presumably a file copy, your file inherited this library ownership -- which you probably want by the way.

The fix you probably want is to open the library and add this VI to it, just like the original one was. Then, once the VI says it belongs to the Library, and the Library claims to own the VI, everything will be happy and the error will go away. To avoid this, in the future, I believe it will work better to do a Save As so that LV will update the library too.

Post again if you need help finding the library or making the edit.

Greg McKaskle
Reply With Quote