I have a large top-level VI that controls and performs data collection
for many different devices and over different interfaces. I currently
do all of the control interactively through the front panel UI. I
would like to have my VI be able to run off a script... not an
external scripting
Thanks for responding, Shane. All of that was very informative. I
still have some comments:
1) Could you elaborate on the statement references [force] everything
through the GUI thread? This kind of makes sense to me, but I
haven't found much info on the web besides using references for
thanks for the comments, ryan. It's always nice to hear from the
people who develop the software.
1) It seems to me that allowing people to pass pointers to complex
data structures would allow for more efficient memory management. I
know about refnums, but Shane and others seem to imply that
I am self-taught in LabView like most people in academic science, but
the main VI I use has finally become sufficiently complex that I have
to worry about memory management and other concepts that beginners
don't normally worry about.
so I read the LabVIEW Performance and Memory Management -
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
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
