Paul, > In LabVIEW 7.0 on my Mac, the launcher stays in memory
The problem goes away if you remove the "Launcher" RefNum from the ConPane. The control's value is being reset to the default value (null) when you invoke the Run method. I think this might be a bug in LabVIEW 7. I believe that the expected behavior is that FP Controls connected to the ConPane are only reset to default values when a VI is "Called" (Statically, using a CBRN, or invoked by the ActiveX "VI.Call" method) not when it is "Run" as top-level (by pressing the Run button or invoking the VI Server VI.Run method). Anyhow, the problem is fixed by removing the RefNum from the ConPane, which doesn't seem to have any negative implications for your App. Regards, -Jim "Paul F. Sullivan" <[EMAIL PROTECTED]> said: > LabVIEWers, > > Prodded by Dan Bookwalter and assured by Rolf Kalbermatter that I was > not overlooking the obvious, I have upgraded Ghost Buster to launch > different code for different versions of LabVIEW. The new release > warns of minimized VIs in LabVIEW 7 and up. Visit > http://www.sullutions.com/LabVIEW.html to read about the improvements > and download the new version (royalty free for personal or company > internal use). > > In LabVIEW 7.0 on my Mac, the launcher stays in memory, even though I > think I have killed all references to it. In 6.02 and 6.1, the > launcher leaves as soon as Ghost Buster 6 is running, as I expect. If > you know what I am doing wrong, please let me know and I'll fix it > in the next version. > > -- > EnWirementally, > Paul F. Sullivan > > ---------------------------------------------------- > > SULLutions (781)769-6869 > "when a single discipline is not enough" > > visit http://www.SULLutions.com > > ---------------------------------------------------- > > --
