NI TestStand Idea Exchange

When putting values into an array of number local variable, there is little documentation specifying the correct way to input values in an array. The documentation needs to be improve and/or the error message that pops when evaluating your statement should be fixed to better demonstrate the problem. The current error states "Variable or property types do not match or are not compatible. This value will cause a run-time error." A getting started documentation that addresses variable syntax would also be helpful, these ideas will improve ease of use for people working in TestStand. The typical syntax when working with arrays is the use of a bracket [] and the error that appears when using a bracket for arrays is even less helpful. Attached is an image of an example of the fixed error that would demonstrate this problem more thoroughly (The red highlighted section would be a potential change to the errors).

For simple operations would be nice to have possibility to drag and drop functions from LV functions palette directly (default step type can be Action)

Currently you can right click the insertion palette and change the position / menu items that are shown / hidden in the insertion palette from a context based dialog box. (can also be done from the same box in the type palettes view).

It would be useful to be able to modify this programatically.

Currently you can only programatically play with the typepalettefilelist from the engine property object and insert new ones or remove old ones.

If a sequence file is loaded that has a step type in it that is not currently loaded by a type palette file, then it shows up in the insertion palette (as it should do), but if the testexec.ini file says this should be set to "hide" then it is hidden.

Thoughts

Thanks
Sacha

So we have the setup, main and cleanup step groups in the sequence view which is fine, and they're collapsable which means if you're working in Main you don't get a screenfull of Setup above you.

We also have block sections that you can associate with step types to provide indentations making navigation easier.

What I'd like to see is the ability to create a collapsible section (so a sub sequence call is NOT what I'm talking about).

For times when a sub sequence call is not necessary, we should be able to insert a block section that is collapsable purely for visual appeal.

It makes long sequences easier to navigate. This would be a visual implementation modification on how we show block sections (so collapse versus indent).

Thoughts?

Thanks
Sacha

With the release of TS4.5 there is new way of .net invocation.

The new look of the .net panel was first strange to me.

I was always searching constructor stuff for defining a handle
But after understanding. It is very easy use.

Add especially the feature with the dots is pretty good.
It seems you are doing your stuff in programming language like VS.
But this leads to a “missing” feature. Which is not possible in VS. 

In TS 4.5 you may store every return value in a variable.

If your invocation consisting of many “.” calls. You only see the return of the bold function.
So this feature makes some return values “invisible”.
Maybe a tree or using some other colours should make them visible again

Regards

Juergen