01-18-2011 01:42 PM
I'm a LVOOP NOOB. I've got an object and I want to write it to file and read it back in at a later date.
Are there any conventions out there that you'd recommend?
A really easy way to do it would be binary file, but then that will cause problems if the properties ever change. Obviously, I could go XML but I'm not that up on any easy ways to do that - seems like a lot of coding is required.
Seems like I recall seeing something at NI Week about LVOOP files that auto-handled changes to properties. Don't remember the details - or did I just dream it?
Thanks for your input.
01-18-2011 01:49 PM
True dream!
I have not tested out every possiblity but yes will read a file writtein with the old class def and put it together in the new def. and can handle updates. It is not 100% fool-proof (nothing is fool-proof to a clever fool) so if a clever fool saved in version 1, delted a field in version two and then add it back in version 3, well you loose the history when the widget is deleted so ti will not go back into the first version.
Try it out for yourself and please let me know if;
A) I have been drinking too much kool-aid (and it does not work)
B) It works as advertised but watch out for...
Ben
01-18-2011 03:32 PM - edited 01-18-2011 03:33 PM
Here are some relevant links: