LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

making a standalone app that does not run when opened

i have a project. when i go to the stand alone aplicaiotn build prefs. under "source file settings" for the startup app, i played with
the "Run When Opened" setting an no matter how i set it the application runs when opened. how do i stop it from running when opneed. i want to be able to change setting before it runs.

thanks.

-evren
0 Kudos
Message 1 of 9
(3,927 Views)
Hi Evren,

In LV 8.2 there is a bug that prevents this.

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!
0 Kudos
Message 2 of 9
(3,924 Views)
I am now convinced ( that I will not be able to create standalone applications using the  Application Builder )

For the all beauty of a software that LV is , there has been some ( very serious ) issues with the Application Builder software. This is one software that I paid for and bought it but have not been able to put to use the last  so many months. Despite reading and trying it out so many times with so many options.

Sad indeed.  In fact converting the design module of any code into a free standing application, calls for lots of  "background" and registry level work by the software meant for it. ANd it should abstract the user from this mess and offer a smooth interface. ( like the Deployment Wizard in Visual Studio )

Raghunathan


Raghunathan
LabVIEW to Automate Hydraulic Test rigs.
0 Kudos
Message 3 of 9
(3,922 Views)
I've never had to do any registry work with the application builder.

Works nice and smooth for me.

Of course I'm using LV 6.1 so that may make a difference.

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 4 of 9
(3,907 Views)
>> I've never had to do any registry work with the application builder.

Not that I had to or intend to !

I was just mentioning  this, as after creating an installer for a data logger code, all my LV7.1 and LV8.0 have gone for a toss and everytime I launch them, an Installation program is launched  which keeps pestering for " lvruntimeeng.msi "  I have searched the entire C-Drive for this offending .ini file or some such thing and could not find one. Hence I presume that some changes have been made to the registry.

The obvious and time tested answer would be to uninstall LV7 and LV8 - and reinstall. And you know for what - just because I wanted to use Application Builder....

Raghunathan

Raghunathan
LabVIEW to Automate Hydraulic Test rigs.
0 Kudos
Message 5 of 9
(3,902 Views)

thanks for the quick help. thought i was goin crazy since the switchs for this were not changing anything.

is there something in the works to fix this bug?

thanks again.

evren

0 Kudos
Message 6 of 9
(3,891 Views)

@evren wrote:
i have a project. when i go to the stand alone aplicaiotn build prefs. under "source file settings" for the startup app, i played with
the "Run When Opened" setting an no matter how i set it the application runs when opened. how do i stop it from running when opneed. i want to be able to change setting before it runs.


@evren wrote:
is there something in the works to fix this bug?

I don't consider this a bug. A built application is designed for the end-user, and the end user should not have to learn LabVIEW specific operations such as the RUN button. 😉

Just design your code so  the program starts up in a wait loop where all controls can be changed, then add a button that swtiched to the more interesting parts of the program. 😄

(If you really want to immediately stop the program at first launch but not at subsequent runs in the same session, I'm sure you can even program this using e.g. an uninitialized shift register and a case structure containing a stop function, etc. But why?)

Message Edited by altenbach on 10-03-2006 09:04 AM

0 Kudos
Message 7 of 9
(3,883 Views)
labview is also used by people that know how to hit start. i would consider it a bug becuase there seems to be an option in the build preferences that allow you to not have this happen. when i select it that way it still runs on start up. am i not understanding that setting in the build prefs to not run on startup?

i understand your point but i would like to have the option to allow it to startup running or not.

thanks for the wait loop suggestion i will use that for now.


0 Kudos
Message 8 of 9
(3,875 Views)
Another workaround is to create a reference to your main VI and set the FP.Open property to true, which will just open the front panel without running the VI.

Nathan
0 Kudos
Message 9 of 9
(3,840 Views)