This is expected behavior. Both the Open VI Reference and the menus are handled by LabVIEW's root loop. The root loop can handle only one item at a time. Open VI Reference by path requires root loop. If you open a menu, the rootloop is unavailable so the Open VI Reference will block. You can workaround the problem by not opening a Reference by path inside the loop. Either open the reference once outside the loop and use that reference or use Open VI Reference by name instead (which requires the VI to be in memory).
Hope this helps!
Message Edited by Kalin T on 04-06-2007 03:40 PM
let me brief what exactly the problem is and where we are facing a problem.
our application is a test application in which end user writes a script for testing UUT as per his needs. for every command in the script there is accompanying VI which is invoked to run that command.
now this list of commands is ever expanding as the product takes more and more features, so we want a plugin type architecture. where if we design a VI and put it in perticular folder, a new command is made available for scripting.
an we have been successful in doing so. everything works fine in normal situation, but we found one bug.
now lets say one script is executing and during that time if end user drops down menu(and keeps it hanging down instead of selecting any item) then the execution of script pauses.
after tracing down we found out that the open Ref VI doesnt runs (but pauses) in perticular situation. we posted the query and we got the reply above. now Open ref VI is not pausing (as we are opening ref by name) but when we try to run the VI using invoke node the invoke node for Run VI Pauses.
how can we tackle this problem?
as such there is no error being generated, but we want to eliminate this pausing.