Re: Hiding Main VI's Window in built application
Yonatan Tidhar wrote: Yes I thought so, but way should the execution should be depend Were the front panel is open or not? No meter if I leave open reference to the VI I was expect that the vi execution will continue until the code ends. As I recall, this was the behaviour a few versions back and could result in a complete inability to terminate the VIs, short of exiting Labview. The present behaviour, as I understand it, is part of some improved housekeeping and cleanup mechanisms. -- Dr. Craig Graham, Software Engineer Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
Hiding Main VI's Window in built application
Hi All, A colleague wants to build an application where a Password dialog appears and only if the correct password is entered would the main VI appear. As I see it, he has 3 choices: 1) Launch Password which then uses VI server to launch Main VI 2) Embed the password VI in the Main VI, but move the Main VI off-screen 3) Find a way to have the Main VI not show until the password is entered. Number 3 is the interesting one. This is all a long way of asking: can one not show a Main VI's window when it launches as a built application? Thanks (in advance), E. Blasberg iDAQ Solutions Ltd
RE: Hiding Main VI's Window in built application
Yonatan Tidhar [EMAIL PROTECTED] wrote: Yes I thought so, but way should the execution should be depend Were the front panel is open or not? No meter if I leave open reference to the VI I was expect that the vi execution will continue until the code ends. Simply because it is way to easy to close the top level front panel (x in top right corner of window for instance) and if an open reference, which was forgotten by the programmer, would keep the VI alive, you would end up with zombie processes. Basically it is protection of the (not so innocent) average LabVIEW programmer, who does not want to deal with proper resource deallocation once he is done with what he wanted to do. You can work around this by keeping a top level VI which starts up all the rests and gets neatly hidden by moving it off screen. Rolf Kalbermatter CIT Engineering Nederland BVtel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijkhttp://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
Re: Hiding Main VI's Window in built application
From my experience (6.1) At the top level VI: A) if I use property node FP.Open and wired False Value to it and the reference input is empty at run time when the property node is called the vi FP is close and the vi executing terminated. B) If I open reference in the top level vi to it self and wire it to the property node the FP panel is close and the vi keep running. C) In the executable app the top level vi FP is show always - I think the show FP when load is ignored. my question are: 1) way did closing the front panel of the vi is stop the vi execution (case A)?. 2) can I build app that the top level vi FP didn't open by default (silent mode)? Yonatan Tidhar X-Sender: [EMAIL PROTECTED] Date: Tue, 24 Feb 2004 09:37:12 -0500 To: E. Blasberg [EMAIL PROTECTED] From: Scott Hannahs [EMAIL PROTECTED] Subject: Re: Hiding Main VI's Window in built application X-NHMFL-MailScanner: Found to be clean At 11:41 +0200 02/23/2004, E. Blasberg wrote: A colleague wants to build an application where a Password dialog appears and only if the correct password is entered would the main VI appear. 1) Launch Password which then uses VI server to launch Main VI 2) Embed the password VI in the Main VI, but move the Main VI off-screen 3) Find a way to have the Main VI not show until the password is entered. I think #1 is a clear winner. First you throw up the password dialog, but in parallel, open a reference to Main.VI. This will cause the Main.vi to load while the user is entering the password. Ah, but doesn't loading the Main show its window (exactly what he's trying to avoid?) No. Opening a reference to a VI does not open its window unless it has been set to open window when loaded in the VI properties. You have to have the main vi, explicitly show its front panel when it is called by the password vi. Or you can have the password VI show the front panel, just before it runs the main VI. There is an example: http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123A E0CB932111EE034080020E74861p_node=DZ52054p_submitted=Np_rank=p_answ er=p_source=External (watch out for line wraps by your email client!) -Scott ** The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. ** eSafe scanned this email for viruses, vandals and malicious content. ** **
Re: Hiding Main VI's Window in built application
Because in A, once you close the front panel there is no reference to the VI, unless it has opened its own reference. At 1:38 PM +0200 3/1/04, Yonatan Tidhar wrote: From my experience (6.1) At the top level VI: A) if I use property node FP.Open and wired False Value to it and the reference input is empty at run time when the property node is called the vi FP is close and the vi executing terminated. B) If I open reference in the top level vi to it self and wire it to the property node the FP panel is close and the vi keep running. C) In the executable app the top level vi FP is show always - I think the show FP when load is ignored. my question are: 1) way did closing the front panel of the vi is stop the vi execution (case A)?.
RE: Hiding Main VI's Window in built application
Yes I thought so, but way should the execution should be depend Were the front panel is open or not? No meter if I leave open reference to the VI I was expect that the vi execution will continue until the code ends. Yonatan Tidhar Bae systems ROKAR International Ltd -Original Message- From: Scott Hannahs [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 21:11 To: Yonatan Tidhar; [EMAIL PROTECTED] Subject: Re: Hiding Main VI's Window in built application Because in A, once you close the front panel there is no reference to the VI, unless it has opened its own reference. At 1:38 PM +0200 3/1/04, Yonatan Tidhar wrote: From my experience (6.1) At the top level VI: A) if I use property node FP.Open and wired False Value to it and the reference input is empty at run time when the property node is called the vi FP is close and the vi executing terminated. B) If I open reference in the top level vi to it self and wire it to the property node the FP panel is close and the vi keep running. C) In the executable app the top level vi FP is show always - I think the show FP when load is ignored. my question are: 1) way did closing the front panel of the vi is stop the vi execution (case A)?. ** The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. ** eSafe scanned this email for viruses, vandals and malicious content. ** **
Re: Hiding Main VI's Window in built application
At 11:41 +0200 02/23/2004, E. Blasberg wrote: A colleague wants to build an application where a Password dialog appears and only if the correct password is entered would the main VI appear. 1) Launch Password which then uses VI server to launch Main VI 2) Embed the password VI in the Main VI, but move the Main VI off-screen 3) Find a way to have the Main VI not show until the password is entered. I think #1 is a clear winner. First you throw up the password dialog, but in parallel, open a reference to Main.VI. This will cause the Main.vi to load while the user is entering the password. This makes things run much smoother from the user perspective it Main.vi is any reasonable size. Then just run main and not wait for it to finish and exit the password VI to get it out of the way. Then just make sure that main will open a refrence to itself so it stays running. This is just a modification of the splash screen technique discussed here at great length, only the splash screen has a password. There are probably some examples in someones archives! -Scott
