swenp Posted March 18, 2011 Report Share Posted March 18, 2011 (edited) The LabVIEW help for the "Open VI reference Function" says If you wire a path, LabVIEW waits until the user interface is idle to load the VI from disk. If you wire a name string, LabVIEW does not need to wait until the user interface is idle, as it does not load a VI from disk. LabVIEW will only search in memory for a VI with a specified name. But this is not true if you wire a strictly typed VI reference to the type specifier input. In this case the open reference is blocked as long as the user interface is active, e.g. the user is navigating through the menu. Is this an expected behaviour? Cheers, Swen Dyn.vi Main.vi Edited March 18, 2011 by swenp Quote Link to comment
John Lokanis Posted March 18, 2011 Report Share Posted March 18, 2011 As far as I know and have experienced, Open Reference in VI Server is always blocked by the root loop, regardless of what you pass to it. This makes for some interesting headaches if you have a system that uses dynamically loaded plug-in test modules that are opened as needed while a process runs. The user can effectively hit the 'pause' button by simply dropping down an menu and not making a selection. I have no idea how to work around the problem. Maybe one of the NI gurus can chime in... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.