View Single Post
  #2   Spotlight this post!  
Unread 09-02-2013, 20:03
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: Image Dst issues

Because of their memory size, the vision team chose to expose allocations to the user. This means that they are a bit more fiddly that normal LV data, but it isn't that hard or dangerous.

If you look at the left of the typical vision diagram, you'll see that some images are Created and are wired in as dest images to other blocks. These are typically not deallocated and are used over and over, so no need to close them.

Make sure that you set the image depth correctly or you'll get runtime errors about the destination not being compatible.

Greg McKaskle
Reply With Quote