LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Key Config VI or XML File?

Solved!
Go to solution

Hello:

 

I want to save some configuration values that I want to load when the program executes again after close it. My program have a lot of clusters.

 

Which is better: use a Key Config VI or XML File? I test both and...

 

If I use the "Key Config VI", I can use the same file to save all the values of the different cluster but the program is bigger and more complicated because it doesn't accept clusters directly and I must save values one by one.

 

If I use the "XML File", I must create a lot of files (one for each cluster) but it's easier to save values because it accepts clusters.

 

Therefore, which is better or which do you choose? Any other suggestions?

0 Kudos
Message 1 of 6
(3,252 Views)

Why don't you combine the strings that each Flatten to XML function gives you into a large string that you write to one file?

Chris
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 2 of 6
(3,249 Views)

The OpenG config API is pretty cool

_____________________________
- Cheers, Ed
0 Kudos
Message 3 of 6
(3,246 Views)
Solution
Accepted by damos

@yenknip wrote:

The OpenG config API is pretty cool



I agree with yenknip. There is an Open G vi to save (and retrieve) a cluster to a config file using variant. Make your clusters Type def, If you need to modify them it will save you a lot of work. 

 

Ben64

0 Kudos
Message 4 of 6
(3,242 Views)
0 Kudos
Message 5 of 6
(3,226 Views)

Thank you for all of your answers.

 

I've used The OpenG config API. It's very useful!

 

 

0 Kudos
Message 6 of 6
(3,204 Views)