View Single Post
  #6   Spotlight this post!  
Unread 02-03-2014, 08:51
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: Display processed images on Dashboard?

An image display is essentially given the name of the image to display. When the OS gives us a draw message, it will draw the current state of that named image. But of course your imaging loop may be somewhere else and may have put raw data into the image. So you will get a statistical sampling of what is in the image over time -- not necessarily what you wanted, but it uses minimal memory.

If you make more than one named image using Create Image. You can have two names and decide which you write to the display. Your Boolean switch can sometimes send the raw and sometimes send the processed. Since you won't be using one named image for all the processing stages, the statistical display is always what you want.

Another easy thing you can do is to right click on the image display in the code you have and select to Snapshot the image data. This will make a copy of the image data instead of the name. For simple image processing, this tends to work, and I believe is always on in probes.

Greg McKaskle
Reply With Quote