stopping pda using X button

[vsaone]

Hello,

I have a LabView PDA app that will be deployed to a community of non-savvy users.  Currently the app VI can only be stopped by means of a boolean control.  However, it would be more desireable to also kill the app when the upper right X button is clicked. In Windows CE, this button does a minimize, but does not stop the app.  This has my users confused, since they are used to killing programs using the X.  LabView PDA does not support the Front Panel Window State Property, so I cannot figure out any way to kill the app using the X.  Any suggestions?

Thank you.

Jerry

[tst]

The only thing I can think about is that you check whether the Panel Resize or Panel Close events are available in the PDA module.

[markfranklin]

you could also do away with the X so the only way to stop it is by your boolean button. It works in the way that Sub vi dont have the X in the upper right hand corner so your main VI all it does is calls your sub VI which is really your main VI Check NI examples for how to remove the X button from you PDA App this should explain everything you need to know.  This way you dont have to worry about anyone getting out of the app without closing it the right way

[vsaone]

I tried this approach but ran into a problem.  I turned the main VI into a renamed subVI and created a Main VI that is identical to the PDALauncher vi  in the example (except I substituted my subVI for the one called by the example).  Now, whenever I try to build the app, I get an pop-up small box from LabView that says simply "Bad VI" and simultaneously shows the Error Box that has a big red X error indicating there is a fatal error in my former main VI (which is now a renamed sub VI).  However, the "Bad VI" error message box is a modal pop-up box that I must click OK until anything will continue.  After I click on OK, the sub-VI error indication immediately goes away in the standard Error Box and the Error Box changes to indicate there are no VIs with errors, but the build does not proceed.  So I get no indication at all from LabView about what the problem is and I cannot proceed with a Build.

Any help will be appreciated.

Jerry

[Brian_R]

I might suggest using the example as a baseline and modifying it for your code.  You can cut/paste your code into the example sub-VI.  It sounds like there is a property setting that may be causing an error, but if you use the VIs that are known to work and just insert a few pieces of code, you might have better chances for success.

[vsaone]

Brian, et. al.

I took your advice and that cured the problem. 

Thanks to all for your help.

Jerry