Thread: Ethernet camera
View Single Post
  #10   Spotlight this post!  
Unread 06-09-2008, 08:09
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: Ethernet camera

Quote:
Originally Posted by kamocat View Post
Cool. I had just run into some silly stuff like color to RBG being locked.
That is pretty silly. That VI calls back into a LV entry point, and unless that sort of thing is locked down, people will start calling into it as well, but without the wrapper, the parameters may not get conditioned -- leading to crashes. And if/when we change the interface, we can also change our wrapper to match. If other locations are calling the interface, we have to honor the old interface as well or break their code.

Anyway, the reason the color stuff has to call back into LV is for the symbolic colors. The LV color picker and managers tap into the OS colors such as Window BG, Text FG, Text Selection, etc. That color lookup is the primary thing that the callback into LV handles.

Greg McKaskle