LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

exit behaviour labVIEW 8.2.1.

Hello,

is there a major change regarding the EXIT-Function behaviour from LabVIEW 8.0 to 8.2.1 ?

i recently switched to 8.2.1 but my application exit behaviour is really strange after the upgrade.
I am using the EXIT LabVIEW  Function (True-signal connected to the EXIT Function)


pre-description:
--
* user pressed EXIT
* Are you sure dialog
* Application get closed....no more windows viewable.

post-description:
--
* user pressed EXIT
* Are you sure dialog
* Application is ended. Application windows / Frontpanel is still viewable and Top Bar shows the stopped icon.

why is the offcially EXIT function no longer working as supposed ?
any suggestions ?


Best regards
f.poeck


0 Kudos
Message 1 of 11
(4,144 Views)
Hi f.poeck,

for me the EXIT function ends LabView even without asking - as aspected.

When you talk about application do you mean executables created from Labview or simple vi's in the development environment?
What kind of EXIT function? For me there is no 'Are you sure' dialog...
Can you attach an example?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 11
(4,131 Views)
Hi,

ok my first description was maybe a bit short, sorry.

In my last release (*.exe, created using Application Builder) of my LabView 8.0 (now 8.2.1) project the user had a EXIT Button.
If that button was selected a dialog poped up with the "Are you sure"-dialog. That part was handcreated in LabView and has notihng to do with the LabVIEW-EXIT Function i am using in the next step.

NOW (next step)
If the user answers YES a true-constant is passed to a LabVIEW-function called "Quit LabVIEW". Big EXIT Text on it.

in 8.0 that true constat was enough to close my application and close the appluication windows.

in 8.2.1: the application get closed, but still displays the application windows as non-running application.

Was that enough as description ?
Sorry but i cant post the full-program-source here...would mess everything up i guess regarding size etc...

I have already noticed that some other LV users (german unofficial forum) seem to have a problem with the new function of EXIT / Quit LabVIEW thing.

Best regards
f.poeck
0 Kudos
Message 3 of 11
(4,120 Views)
Hi f.poeck,

I'm using the EXIT function also in my executables created in LV8.21 - and all my executables close their windows when this function gets called.
Btw. I'm using the english LV version on a German WinXP - but this shouldn't make a difference.

For checking this behaviour could you create a simple project containing just a vi with a delay (of let's say 2 seconds) and the calling the exit function. Supply this vi as well as the exe created from it. Then we can check the behaviour on our run time environment too.
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 11
(4,117 Views)
Hi again,

i have just finished the small sample and am realizing that it works there.
Means: in theory you are right.

Now the only thing i have to do, is finding the differences to my Main-Application.....

Do you know any Setting which could cause such a behaviour ?
i.e. in VI Settings -> Window-Prefs or similar ?


Best regards
fpoeck

Message Edited by fpoeck on 08-07-2007 08:27 AM

0 Kudos
Message 5 of 11
(4,109 Views)
Hi f.poeck,

I don't know of any setting preventing the exit-function to really exit.
But maybe the (nearly) 'Knights of NI' can help here?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 11
(4,104 Views)
Are you sure that your code is not ending before the exit function is called?  you can out the exit function under debugging to verify this. 
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 7 of 11
(4,090 Views)
Hello

i am using BreakPoints to be sure.
The signal is reaching the EXIT-Function and exactly at that moment the application itself is ended & the application Window goes in that unwanted mode.
still displayed, as non-running LabVIEW App.

You can see the application-windows-mode-change in the attached screenshot


0 Kudos
Message 8 of 11
(4,069 Views)
Hi f.poeck,

we believe you on this problem, but maybe it would be better to see the block diagram instead of the front panel Smiley Wink
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 11
(4,064 Views)

One change from the pats is the APPLICATION INSTANCE CLOSE? event.  Is it possible that you are filtering the application instance Close Event therefore bypassing the shutdown procedure?  I have not used the silent shutdown boolean but this could be a clue to the change in behavior.  Just a guess bu migh be worth looking into.

 

Paul

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 10 of 11
(4,043 Views)