I just learned how to use property nodes and refnums to modify the
values of individual controls inside of a type-defined cluster. But
when I incorporate this into an existing and working VI, a weird thing
happens: the VI works exactly as it should when it is running, but
when I quit the VI, the
You can create reference for individual element in the cluster
explicitly. To do so, right click on an element inside the cluster,
goto Create Reference. See if this helps.
-Joe
Thanks for the feedback, Joe. I tried using references to the
individual clusters B1 and B2, but that did not alleviate the problem.
Though I still do not understand why I am having this problem, I
have (somewhat) isolated the source of the problem to the following
location: my main VI has a
So it turns out that I am making a common mistake and that, had i
done a little more research before posting this question, I would have
found my solution in the huge debate about CLOSING REFERENCES.
Anyway, the short answer to my own question is that I needed to close
all references that were
whoops, that second link is not right. here's the correct one:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=135HOID=5065000800834CUCATEGORY_0=_49_%24_6_UCATEGORY_S=0USEARCHCONTEXT_QUESTION_0=closing+referencesUSEARCHCONTEXT_QUESTION_S=0
It might worth to try to close the reference after each loop.
Creating a reference is an expensive (CPU cycles) operation. If the
reference is closed, labview will close them when closing the VI, so,
the longer it runs, the longer it takes to clean the memory.
-Joe
sorry, only after posting my comment did I noticed your own response.
You got it!
-Joe
