Leaderboard

And for those who like compact lists: https://www.tldrlegal.com/l/freebsd (2-clause, GPower's article) https://www.tldrlegal.com/l/bsd3 (3-clause, Shaun's highlight) https://tldrlegal.com/license/4-clause-bsd (4-clause, the original BSD license)

Using the Variant to data, turn it into an array of variants. If it returns no error, then your input is either an array, or a cluster. This trick can also turn a cluster into an array of variants so you'll need to check for that too. Maybe check to see that all the data types of the output are the same? But even that isn't a guarantee. How did you end up with an array that thinks it is a variant? Maybe there is an unnecessary To Variant in there some where.

I've created an example for you. XY-GraphSelection.vi

Summary: When dealing with the XML DOM functions if you close any reference to the DOMDocument and try to use another reference to the DOMDocument, LabVIEW crashes. The DOMDocument references do not appear to count properly. See attached VI: crashtacular.vi Steps to reproduce: Open attached VI, set a path to a file which will be written. Execute the VI. Notice how the execution succeeds, and the file is written. Open the block diagram of the VI. Look for the following code... Note the call to NI_XML.lvlib:Close.vi in the diagram disabled structure. Swap the cases such that the close call is made. Warning! This will crash LabVIEW, make sure you've saved any other data you have open: Execute the VI. Expected behavior: After obtaining a new reference to the Document, I expect I should have to close it as I would any other reference I obtain dynamically. I'd only expect the Document to fall from scope after the last reference to it has been closed, instead closing any reference appears to destroy the data. This bug has existed as long as I can remember, but after being bitten by it again I decided to try to document it. What are your opinions? My $0.02: It's a bug. If it's by design, it is at best inconsistent with how references are used in the rest of the library, let alone the rest of LabVIEW or programming in general. I see no mention of it in the list of known issues, however I've seen previous posts regarding the issue over at ni.com in the past. -Michael