01-14-2008 03:04 PM
01-15-2008 11:24 AM
01-15-2008 12:45 PM
This is how it is normally done, but does not work with the IMAQ control. This worked in 7.1 but in 8.5 the reference to the IMAQ control is not working. Yes I can create a reference to a imaq control but when I try to make it into a control that is a reference to a imaq control type this will not work. I cant create a subvi (create subvi selected on a portion of code) if the reference wire to the imaq image display is used nor can I create a generic reference and set it to be an imaq display. It is as is 8.5 does not have an imaq display in the control hiearchy. The only work around is to import a vi I created in 7.1 and copy and paste the control reference into the new vi. Very bizar behavior. Can you do this on your 8.5 is it a universal bug? Is something wrong with my 8.5 I have tried this repeatably on another install.
Paul
01-16-2008 02:29 PM
Hi Paul,
It looks like it is an issue that is still being looked into for future releases of LabVIEW. The workaround appears to be casting the reference to a more generic class and then in the subVI casting it back to the more specific ImageControl class. Here are a few threads that talk about the issue and provide some example code for the workaround.
http://forums.ni.com/ni/board/message?board.id=170&message.id=213405&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&thread.id=196345&view=by_date_ascending&page=1
01-17-2008 07:34 AM
The workaround I have done is to save a vi with the control refernece in it from vision 7.1 then import it and copy into the vis as needed. This is a rather big bug for anyone doing vision. I have many projects with vision so I hope it gets fixed soon. Thanks for confirming that I havent completly lost it and it was a bug not my own stupidity this time.
Paul
01-17-2008 07:34 AM
01-28-2008 08:53 AM
01-28-2008 09:37 AM
The current workaround works fine in both debun and executables in 8.5. I control the top level imaq display from the subvis but it is just an anoyance that I have to use a workaround.
Paul