Programmatically Set Values to Default While Running VI

[aNIta B]

It'd be great to be able to use the "Set current values to default" invoke method while the program is running to grab the current values that a program has.  As it is now, you have to stop your program and open another program that references the first program to set the values to default.  This almost completely defeats the purpose of setting those values programmatically (I might as well go to the File menu).  I'd like to effectively "grab" front panel values and keep them for the next time the program runs.  I know I could do this with file writing- but it'd be nice to use the invoke node as it seems it should be used. 

[smercurio_fc]

The fundamental reason is that you cannot do this at runtime - it's an edit-time operation only. It's the same as trying to set current values to default with an application. You can't because that requires modifying the executable. It's no different in other development environments.

[AristosQueue (NI)]

1. There can be all sorts of situations in which LV has constant-folded the default value case of a subVI to make it perform better. Changing the default value at runtime could (depending upon the optimizations that LV figured out it could apply to the VI) require a recompile.

2. Even if we don't have any reasons to recompile, changing the default value is a change requiring saving. You cannot save a VI in a built application. It would be misleading if you wrote your whole app in the dev environment using the default value to store settings for your VIs and then it just didn't work in the built app.

[jacemdom]

Couldn't you put a brekpoint after the executed VI and then abort everything? This way you would end up with the current values on the VI FP.

[Darren]

Any idea that has received less than 8 kudos within 8 years after posting will be automatically declined.

[JÞB]

I'd argue it as "Already Implemented" and remind people about data-logging.