Hash Table implementation

[ramjeev]

Hi,

Is there a way to implement CVI "HashTableType" equivalent data type in TestStand?

Regards,

Ramjee V

[j_dodek]

Hi,

What do you like to perform with the hashtable inside TestStand ?

Just give us more input ?

There is a way to use array of containers like a mappingtable or dictionary

in Teststand

Regards

Juergen 

[ramjeev]

Hi,

I have a structure in CVI that uses the hashtable type to read the data from a configuration file to search for a key. The same structure i need to get reflected in TestStand to use these strucutre values for the rest of my sequence.

So, Please suggest me a best solution to do this kind of implementation.

Regards,

Ramjee V

[j_dodek]

Hi Ramjee,

Yes you can you approxiamte with a custom data type your CVI structure.

Note: for each Property in our data type you have be defined the the 'C' datatype.

         and dont forget the alignment.

There is also good example \Examples\StructPassing\C\Struct Passing to C DLL.seq that comes with TS

Regards

Juergen

[James_Grey]

Instead of duplicating data, you could export the functions you need to access your data structures from your CVI DLL and call those from TestStand.

[j_dodek]

HI James,

I am interrested in your recommondation. 

Where would you prefer to store data TS or DLL ?

(I know that will be depends on the app, but what are in pro and con in your point of view?)

Regards

Juergen

[James_Grey]

If your data structure is complex enough to require accessor functions and it is already implemented in CVI, it would be simpler and faster to access the data via CVI functions. If your data is not global, you'll need to pass a pointer to it back to TestStand for TestStand to hand back to your accessor functions.

If you need to be able to inspect and access the internals of your data structure in the TestStand variables view or in expressions (unlikely if you have good accessor functions), or if your data structure is a structure you want TestStand to convert to the languages of other modules such as LabVIEW or .net, then you might want to put it in TestStand.

An analogy would be an instrument driver. Instrument drivers have all sorts of internal data structures, but you typically only deal with their exported functions (and the instrument handle), whether calling them from TestStand or CVI.

[j_dodek]

Hi James,

Thanks for answering, your statements will cover with my one's.

Regards

Juergen