NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

List of currently loaded types

Hello,
with SequenceContext.Engine.GetTypeNames() I get an "An array of strings that contains the names of all the currently loaded types", according to the documentation. It seems that this lists only data types which actually exist in the current SEQ-file.

How do I cause a type to be "currently loaded" resp. how can I get a list of all types currently known to the engine, i.e., everything that would be listed in the Type palette under "All types"?

Best regards,

Peter

0 Kudos
Message 1 of 5
(3,575 Views)

Hi Peter,

What version of TestStand are you using?  When I lay down an Expression Step in TS 4.0 and set Locals.myArray = RunState.Engine.GetTypeNames()  Then I get 140 elements in Locals.myArray.  It looks like all the types in my type pallettes are in the list.  I am doing this from the Sequence Editor. 

What are you seeing if you do something similar?  How many elements get returned for you?

Regards,

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 2 of 5
(3,573 Views)
Hi jigg,

I see the same behavior that I described under TestStand 3.5 and 4.0. I  guess the difference is that the step I am using, uses "SequenceContext.Engine", not "RunState.Engine". Have to change some source code to check that, will get back to you with the result.

Thanks a lot.

Peter


0 Kudos
Message 3 of 5
(3,570 Views)

So I passed the Sequence Context to a LV VI and grabbed the engine and then called the GetTypeNames() method from an invoke node.  Then I get that returned as a Variant.  I converted that to an array of strings and passed it back to my sequence and it looks the same as calling RunState.Engine.GetTypeNames(). 

Just a little more from my end.

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 4 of 5
(3,566 Views)
Hi jiggawax,
 
I just noticed that in the hectic I forgot to thank you for your message and to tell you that, indeed, I get the complete list; the list got filtered on a completely different level in our software.
 
Thanks again,
 
Peter
0 Kudos
Message 5 of 5
(3,476 Views)