call setup, load or unload vi in memory

[Norbert_B · Accepted solution]

I understand, that this is confusing. Honestly, i am surprised that the documenation isnt more clearly against the observed behavior.....

The point is, that your Call by Reference can only call a single VI as you entered the path to the VI hardcoded. Therefore, LV can (and will) check if that VI is available and it will make sure that it can be executed smoothly.

I would expect that to be the reason for the VI to show up in the "VIs in Memory" list.

IT DOES NOT SHOW IF THE VI IS RUNNING OR THERE IS MEMORY ALLOCATED FOR THE VI!

So essentially, the call reserves a handle, but locks it only if required. Locking the handle will also allocate memory for the subvi. If the handle is unlocked, the memory can stay allocated, but might be used for other VIs.....

Norbert

[superglglgl]

Norbert,

i think, you are completely right. thanks a lot.

Lei