Save user input data

[HYDAC_R_and_D_Lab]

I would like the ability to have a settings screen and allow the user to enter parameters.  These parameters need to be saved even when the program (VI) is shut down.  As an example I made a quick simple program, Sample test 1.vi.  Here there is input data, amplitude, a maximum setting and a minimum setting.  I would like the user to be able to set the settings (maximum and minimum) to the desired level, run the program, stop the program, shut down the program.  Upon restarting the program the settings should be at the last entered value. Any ideas or assistance is appreciated. Thanks,Brian

[GerdW]

Hi Brian,

save the settings to an in file (aka config files) on exiting the settings dialog...

[JÞB]

Great tip!  even LabVIEW itself uses this technique!

[HYDAC_R_and_D_Lab]

Jeff, Correct you are hardily working, not much help.  Obviously if I was more familiar I could shoot a sarcastic comment to myself and get it done.  I am relatively new and have limited programming experience with LabVIEW.  I posted the question to see if someone could help me with my application; perhaps someone keen enough to give me some insight on how it works.  There is always something new to learn—don’s give up Jeff. Brian

[Mark_Yedinak]

Look through the example VIs that ship with LabVIEW. They have examples on working with ini files. I have included an example of the VIs that we use for our applications as well.

[Dennis_Knutson]

Your comments to Jeff are really uncalled for. He was commenting that an ini file is a great idea and that LabVIEW itself uses ini files to save user settings.

All that you have to do is start the example finder and go to the Fundamentals>File Input and Output and look at the read and write configuration file examples.

[HYDAC_R_and_D_Lab]

Yes, correct I did reach harshly.  Sorry Jeff. 

I took it as a sarcastic remark.  My mistake for replying with the message; I feel like an ass.

Brian

[Broken_Arrow]

More or less in order of my favorite to least favorite methods...

• With controls in cluster(s), flatten to XML. Save it as a XML file. Unflatten from XML to read back into Local Variables when program starts back up.
• Use Open G Configuration file utilities.
• Use "keys" individially into INI file. Reading the INI file back is intuative if not bulky.
• Save settings as pure text. Parse text > populate locals.
• Write settings down on piece of paper. > Read from paper, manually populate the screen.

Message Edited by Broken Arrow on 10-02-2009 10:54 AM

[JÞB]

---

Flüssige überwachung wrote:

Yes, correct I did reach harshly.  Sorry Jeff. 

I took it as a sarcastic remark.  My mistake for replying with the message; I feel like an ass.

Brian

---

I've done it myself----- Thanks for the apology.  I Certainly did not mean to sound sarcastic!  But, in my defense, it IS the obvious solution

A "*.ini " saves months of 'whoooooops' programing