Jump to content

Chris_Collier

Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by Chris_Collier

  1. Thank you. Implementing this does make the software work as I would expect. This is more steps than I thought would or should be needed, but it should allow me to use versioning implemented as I wanted. Thank you for your help!
  2. I'm building an application (which I am intending to share at a local user group soon), but am having issues with XML file data versioning. My intent is to have a data type which has a version string, and a variant for the data which will be read according to the version number in the version string. The issue is that if you flatten the data type to an XML string with any data in the variant, then try to unflatten the data, you get an error (1106: "LabVIEW: The XML tag describing the type of data does not match the wired type.") How have you done versioning for data files which you are pretty sure will change over time? And can anyone tell me why this attempt doesn't work? Thanks, -Chris Collier P.S. The attached files are in LV 2014 Test XML.zip
  3. Hey all, I'm working on a project which uses Excel spreadsheets as a script to run tests. Something I'd like to be able to do is embed images into the spreadsheet, then call them at points throughout the test. This would be so that all we need to run the test is the excel file, and there won't be any issues if a secondary image file is missing because it wasn't installed at the same time our script was. I have figured out how, in Excel, to embed images into comments which can be associated with cells, but I can't determine how to read those comments in LabView... I would have assumed there would be a "Value" property of a comment, but I can't determine how to get to that. If anyone can assist in either helping me to get picture data into an Excel cell, or by determining how to read the value of a comment, I would appreciate it. Thanks!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.