Enable/Disable "Run when opened"

[Kai456]

Decided to write a program on NXG. I'm building an executable out of it. Is there an option somewhere that'll let me toggle whether or not the application runs when its opened? I can't find it anywhere (or almost any build options for that matter). 

Thanks!

[GerdW]

Hi Kai,

you want to create an executable that does NOT run when you call it?

Is this the way other software (like e.g. Office, InternetExplorer or even a command in the command shell) work?

An executable will always "run when opened"! (That's why it is an "executable"!)

You need to program it in a way your user can use it…

(I guess your user wants to change some settings before the main part of your executable is started: what about a config dialog with an "OK" button?)

[Kai456]

Well, yes. In Labview there's actually a setting for it, so I was wondering if there was one in NXG as well!

[Shalini.M · Accepted solution]

Hi Kai456, 

As of LabVIEW NXG 2.1 that functionality is not available, presumably for the reasons GerdW explained.
Could you elaborate on a use case or explain why you would want the ability to enable/disable "run when opened" so that we can take that feedback into consideration for potential future releases?

[Kai456]

Pretty much changing some settings like Gerd had said. I ended up changing some things around and creating a dialog box like he had mentioned, but having that setting available would certainly have been easier and more convenient! Small reasons like this is why I think I'll be sticking to LabVIEW over NXG for a while longer.

[Jon_bellows]

I'm having the same issue, are there any updates to this as of NXG 3.0?

[altenbach]

---

@Jon_bellows wrote:

I'm having the same issue, are there any updates to this as of NXG 3.0?

---

So you want to disable run when opened? Can you think of any other program (word, Excel, browser, etc) that needs to be run after opening? It is just not a useful option.

Please explain why you think you need that.

[Jon_bellows]

I need the user to configure some settings before starting a test. I think I can program around it, but I was just wondering if there is a short cut. 

[altenbach]

"state machine". The initial state is configuration. No user should have to learn edit environment idiosyncrasies such as a "run" button.