03-24-2014 08:15 AM
I am making an application from which the user can choose to open several non-modal popup windows. The popup windows contain a .net control in them. I believe because of this control the window takes a couple of seconds to close. This is not a problem if it happens "in the background", but the main window freezes while any popup window is closing.
The popup window VIs are reentrant and are opened using Open VI Reference with option 0x80 and Start Asynchronous Call.
Is there something I can do to improve this?
Solved! Go to Solution.
03-25-2014 04:57 AM
I found the issue. I was closing the type specifier VI Refnum, which I apparently should not be doing.
06-23-2014 09:17 AM
Actually I now found that closing the VI only helped with the hanging of the application while waiting for the popup window VI to close. The VI however actually did not close, but was kept in memory until application closed. I also tried using Run VI invoke node method to start the popup VI, but the entire application still hangs for a bit when closing the popup VI.
06-23-2014 09:35 AM
Can you post the popup-vi?
/Y
06-24-2014 01:23 AM
06-24-2014 03:46 AM
Generally it feels like you need to manage and close/kill the .net ref in that VI to avoid waiting until the garbage collection does it.
/Y
06-24-2014 07:33 AM
I am using third party commercial charting control LightningChart Ultimate (www.arction.com). I have attached a simple example. The delay/hang with this VI is shorter than my bigger more complex VI (which can take around 10 seconds to close), but I cannot post that VI. You will need to download and install trial version of the control to test this.
06-24-2014 08:21 AM
I looked at that some 6 months ago, and looking at the C# reference code, don't you need a Invoke->Dispose before closing the ref?
/Y
06-25-2014 02:17 AM
It seems explicitly disposing doesn't make any difference.
06-27-2014 04:59 AM
Hello Roger,
Did you ever experience that NI LabVIEW complains that some methods are not available with the trial version?
It does seem that the trial version (version .NET4) I downloaded predates the version you are using.
If you can help me with getting it to a runnable state at my side, then I might be able to help you further troubleshoot it.