View Single Post
  #3   Spotlight this post!  
Unread 25-01-2009, 11:12
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: Library Access Scope Problems

Glad to see you got it working. That error message is a bit advanced and hard to understand.

What it is saying is that the person who wrote the PWM library didn't expect you to use some of the VIs you were trying to use. So as you dug around and copied and pasted, you copied some of the internals.

You may wonder why anything is protected like this, and again, it is kind of advanced. In some ways it would be easier to keep everything open. But what would happen is that when the author of PWM wanted to change something, they would break lots of people's code. By telling you to use things like Drive, they can make sure that keeps working while being able to add features or improve things internally.

Greg McKaskle
Reply With Quote