From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

VI Call Type Confusion: Class Member Call vs VI Call

Solved!
Go to solution

What is the difference between specifying that a VI is a method member as opposed to just specifying that it is a VI Call from the Call Type drop down menu? I have looked at the documentation, but it seems a bit sparse.

 

Bonus: Is there something about classes that prevents their member VIs from doing the Step Into to debug their block diagrams? When I step into these VIs, they just skip right over the VIs.

0 Kudos
Message 1 of 2
(2,341 Views)
Solution
Accepted by topic author EricEvola

Hey Eric, 

 

The main difference is that you don't get dynamic dispatch when you call through the VI Call option. As for your bonus question, I am not sure why that wouldn't work. I tried this with a static member and was able to step into it and see the block diagram just fine. Was the VI part of a inheritance chain? Was it a dynamic dispatch VI? Did you get an error? Can you step into any VI? 

 

I am not sure if you saw these, but I want them here for reference:

Calling LabVIEW Class Member VIs from TestStand

and 

Passing an Instance of a LabVIEW Class Object

 

Was this the documentation you were referencing? If so, what is missing? 

Kurt P
Automated Test Software R&D
0 Kudos
Message 2 of 2
(2,302 Views)