LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

To Get Control of a VI - Any Programs out there ?

Hello all.

Well I've been working with LabView and have a few questions about
controlling the VI if you make a mistake in programming.

What I have done is wired a switch to the "EXIT LABVIEW" icon and the
logic is wrong. I have also changed some of the setting in the
"Execution Options" such as "Run When Opened" so when I run the vi
from LABView it immediately shuts down. Does anyone know how to
regain control so I can correct the problem . I would thing NI would
have a program or a method of correcting this kind of goof, don't
they?

Also how do you go about making an executable? I've noticed that I
have to setup the "Windows Options" and "Execution Options" before
doing a build which means I ha
ve to save the new program and it looks
like its possible to use "Application Builder" to create the
executable but then you can't edit the VI anymore. So do you just
remember to save a copy of the VI off first and then do the changing?

Does anyone have the setups you would use to make a vi look just like
a windows program? ie. you click on it the program comes up with
only a title bar and the three buttons on the right hand side but the
menus are not there (unless you handle them in the vi) and you don't
have any scroll bars just a box that you can run the program from a
button, stop on the button and exit using a button only? So far when
I was stoping the program with a button when it ended the menu's came
back along with the vi's icon. I don't want the user to see any of
this. It's just run, stop, exit (close the window).

Sorry for rambling on so much its I just don't see anything in the
manuals that talks about how to build a program for different looks.

TIA

Regards,


Steve Drake
0 Kudos
Message 1 of 4
(1,541 Views)
> Well I've been working with LabView and have a few questions about
> controlling the VI if you make a mistake in programming.
>
> What I have done is wired a switch to the "EXIT LABVIEW" icon and the
> logic is wrong. I have also changed some of the setting in the
> "Execution Options" such as "Run When Opened" so when I run the vi
> from LABView it immediately shuts down. Does anyone know how to
> regain control so I can correct the problem . I would thing NI would
> have a program or a method of correcting this kind of goof, don't
> they?
>
> Also how do you go about making an executable? I've noticed that I
> have to setup the "Windows Options" and "Execution Options" before
> doing a build which means I have to save the new program and it looks
> like its possible to use "Application Builder" to create the
> executable but then you can't edit the VI anymore. So do you just
> remember to save a copy of the VI off first and then do the changing?
>
> Does anyone have the setups you would use to make a vi look just like
> a windows program? ie. you click on it the program comes up with
> only a title bar and the three buttons on the right hand side but the
> menus are not there (unless you handle them in the vi) and you don't
> have any scroll bars just a box that you can run the program from a
> button, stop on the button and exit using a button only? So far when
> I was stoping the program with a button when it ended the menu's came
> back along with the vi's icon. I don't want the user to see any of
> this. It's just run, stop, exit (close the window).
>

The first problem can be resolved by one of two ways. You can
drop the top level icon onto a new diagram and double click on
it. This form of edit/open will not execute the VI. The second
technique is to open a subVI that the top level VI uses. Break
the subVI by changing a control to an indicator, add a wire
segment, or whatever you like. With the subVI broken, the VI
will be broken when opened and will not run.

The second can be accomplished using an add-on tool called the
Aplication Builder. It allows you to build an EXE, and an
installer.

Greg McKaslke
Message 2 of 4
(1,541 Views)
> What I have done is wired a switch to the "EXIT LABVIEW" icon and the
> logic is wrong. I have also changed some of the setting in the
> "Execution Options" such as "Run When Opened" so when I run the vi
> from LABView it immediately shuts down. Does anyone know how to
> regain control so I can correct the problem .

From Explorer, you can drag your top level vi to a new untitled block
diagram. When the vi is in the block diagram, double-click on it and it
will launch without running.

> Also how do you go about making an executable? I've noticed that I
> have to setup the "Windows Options" and "Execution Options" before
> doing a build which means I have to save the new program and it looks
> like its possible to use "Application Builder" to create the
> exec
utable but then you can't edit the VI anymore. So do you just
> remember to save a copy of the VI off first and then do the changing?

Either that or just use the above mentioned trick to turn off the "Run
When Opened" so you can do further editing on your vi.

> Does anyone have the setups you would use to make a vi look just like
> a windows program?

Try unchecking "Show Scrollbars", "Show Menu Bar", "Show Tool Bar"
in VI Setup.

>So far when I was stoping the program with a button when it ended the
menu's >came back along with the vi's icon. I don't want the user to see
any of
> this. It's just run, stop, exit (close the window).

When you use Exit in an exe, the app will disappear like a normal program.
I have created a little routine that tests to see if the app is a
development vi
or an exe. (using VI server Application:App Kind ) If you are in
development, use "Stop", if you are in Run Time use "Exit" to close the app.

Alan Brause
0 Kudos
Message 3 of 4
(1,541 Views)
"EXIT LABVIEW"="Quit LabVIEW" does just that what it's name says "Quit LabVIEW"Shortcut Crtl + .     ("." point behind the "+" is not a fly shit on the screen)will close some never ending ... without loosing source."Allow user to close window" has to be enabled in VI setup!!!Race conditions like "One Button Dialog" in an endless loop are difficult to stopwithout loosing source. Sometimes i succeed - sometimes not.MfGManfred
0 Kudos
Message 4 of 4
(1,541 Views)