A GOOP object's data is stored in a cluster. To save and load this from file, create two method VIs called "MyClass Save to File.vi" and "MyClass Load from File.vi". In these VIs you will need to choose the implimentation that writes this cluster to file and reads it back from file. You can save to datalog file, XML, INI, or whatever format you want. But, the drawback is that you will need to impliment this yourself. You will also want to consider the implications of changing the version (structure) of your GOOP object's data store. Will you allow old versions to be loaded? How will the conversion from the old version to the new version be done? Another factor to consider is that objects aren't just data, they can have states that are not achievable simp
ly by reloading thier data store. For example, what if some of the data are refnums? A reference to some other object may loses its context between saving to disk and reloading from disk.
To get you started, the tool that I use to flatten/unflatted GOOP data stores to/from disk are two VIs in the
Variant Configuration File IO library of the
OpenG Toolkit called
Write Key (Variant).vi and
Read Key (Variant).vi. These will allow you to flatten just about any LabVIEW data structure to an INI file format and read it back again.
Best of luck,
-Jim