Set Value as Default Using Property Node? (run-time)

[esa_paranoid]

I was wondering if there is a way to do the following:

When a control value is changed on the front panel of a run-time application, can that value be stored as the default value for that control, so that when the application is exited and then re-opened the last used value loads?  Maybe using a property node?

I am currently writing the values to file and then reading them from file to do this...I was just curious if there is a way to change the default value in a run-time app.

Thanks,

Ryan (7.0)

Message Edited by esa_paranoid on 07-14-2005 10:51 AM

[PauloM]

Hi,

I know how to do that for the complete set of controls of the application (Check attachment), for only one, I never did it.

Hope this helps,

Paulo

[esa_paranoid]

Paulo, thank you for the response but I cannot view the attached file as I have labview 7.0.

Could you possibly save it as 7.0 ?

Thanks!

[PauloM]

Here it is...

[pincpanter]

Anyway, keep in mind that this action modifies the VI itself, so the VI must be editable.
It would not work, for example, in an EXE application.

Paolo

[altenbach]

The method "Make current values Default" is not settable when the VI is running and is not avilable in the run-time engine.

You should probably write your desired default settings to e.g. an *.ini file that is loaded automatically when the application starts.

[esa_paranoid]

Hmmm...that is what I am looking for, in an .exe

So I am assuming the way I am doing it, writing the values to file and then reading them from the file is the only option?

[esa_paranoid]

Altenbach, do you have an example of writing an .ini file and loading an .ini file?

[falkpl]

init file text file or xml file is probably the way to go.  It would be nice if there was a default initialization event for vi's so you can put all your initialize code in there.  I usually make one vi which opens an xml file and loads all controls with the default values,  if the initialize is successful, I run the main loop of a program.  Init files and xml files have the advantage of being able to set some or all values without having to have a strict text file format.  Also placing initialization values in such a file allows for compiled programs to be easily customized and modified at user sites.

Paul

[esa_paranoid]

well i am currently saving the values to the windows registry and loading them before i enter the main program loop...

this also allows for easy editing/setup at the end users location

I am trying not to create files that can easily be deleted or tampered with without some pc experience.

So it sounds like the way I have it is probably the best solution to this problem?