07-05-2007 09:53 AM
07-05-2007 03:08 PM
I am willing to bet that you are using the original displayed image for processing as well. This changes the displayed image, which will update even after you display it. If you do binary processing, the image looks black in most cases.
Your best solution is to copy the image, so you have one called Display and one called Process. Copy the image right after you acquire it, then wire Display to the display and do the processing on Process.
Bruce
07-06-2007 08:46 AM - edited 07-06-2007 08:46 AM
Thanks for your help Bruce,
I've got the image up for most of the time now, with short gaps where the image drops out, a big improvement over what it was. I tried to go about the method you suggested, but in some stages of the processing there are shapes overlayed on the images which I need to be able to see. Using the copy did not allow me to view these overlays. What the program appeared to be doing to draw these shapes was writing to individual image property nodes for each shape and line sub vi. I cleaned this up a by wiring the initial image to one, then the rest to each other, with the final sub vi sending the image out to the display.
Like I said, now there are short periods where the image drops out, which I'm guessing is a function of the while loop that it is in. Still it's working a lot better. Thank you for your help and if you have any more thoughts on the issue I'd be glad to hear them.
Message Edited by JonJovi on 07-06-2007 09:47 AM