Hello I recently upgraded to LabVIEW and Vision 7.1. I have a large application developed in 6.1 that worked great. It does image acquisition
via a Bitflow frame grabber using labview VI's that call their DLL. The application also utilizes GOOP 1.01 that is downloadable from the NI
web site. The problem I think is happening is that the BitFLOW DLL's often map and unmap the pixel pointer. I then try to write the control back to the GOOP objects data member set, but I don't think it is really pointing or holding the right memory location. This is hard to explain, but the acquisition window shows no data, like it is pointing to different memory. When the DLL Maps and unmaps the image is it doing something to the memory space? Can GOOP not hold the image control in it's data set now? If I get rid of the GOOP object and just use the VI's that call the BITFLOW DLL it works fine. What exactly changed on the new control?
Attached is a screen capture of what works and what does not.
John
