LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

2 screens open in dev mode when I open one screen

I have an application that used to work properly, then somehow, LabVIEW just seemed to change the way it was working.  I have written an application that opens a main screen.  This is called "mainscreen.vi".  Inside the main screen vi, when it runs, it opens another vi, called "setup.vi".  The problem I have is that when I first launch LabVIEW, then open "mainscreen.vi", "setup.vi" also opens right along with it.  These vi's are not running upon opening.  Both are in dev mode and are not running at all.  Why would another vi suddenly start opening along with mainscreen?  Whe I open setup.vi by itself, it is the only one that opens.  This is very frustrating, as I am getting tired of constantly having to fix settings within LavVIEW that seem to change all by themselves.  When running the application (exe version), since both screens open upon launch, the setup screen won't go away.  It is set up to close if originally closed, but since it was open from the start, it won't close and release the program back to the main screen.  Please help.
Thanks.
Rick
 
0 Kudos
Message 1 of 5
(3,041 Views)
By the way, this is LavVIEW 7.0
0 Kudos
Message 2 of 5
(3,036 Views)
Go to the VI properties for setup.vi, go to window Apeearance, click on cusomize. Is the show front panel when loaded option checked. Turn it if off if it is, and check if that fixes your problem.
Message 3 of 5
(3,026 Views)
Check in the setup.vi settings the option "Show Front Panel when loaded"
If this is true you get the behaviour you have.

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 4 of 5
(3,016 Views)
That's a no to show front panel when loaded.  I have selected show front panel when called : close afterwards if originally closed.  This is really strange, but I did find a way around it.  I changed the name of the setup.vi to setup1.vi.  Then, I changed the calls within mainscreen.vi to setup1.vi using the replace command.  It works now.  go figure.
0 Kudos
Message 5 of 5
(3,002 Views)