NI TestStand Idea Exchange

Hi,

When you cancel the breakpoint set in the sequence file tab whilst this sequence file is running you can still see it in the execution view.

It's bit confusing, and needs correcting, I think.

Hi,

As in the subject. Now when you would like to do new line by hitting the enter, whilst you are in the Expression Browser - > Expresion field (marked with yellow), the Expression browser gets closed.

It would be good for visibility if the new line creation would be allowed in this field.

Sometimes in the tests we would like to check are they any common elements for two arrays.

TS2013 have a nice function called Contains() using which devs can easly check if the searched element is in the array or not.

And what about the function which returns an array of common elements of two even more than two arrays?

Instaed of looping one array and issuing Contains() command it would be good to have a kind of logical AND using which we can have a list of common elements?

Would the operator overloading be the right things to do?

Hi,

I propose to that the steps to have new feature called AllowableCallers.

Using this feature developers could restrict the callers (subsequences) from where the particular steps could be called.

Having this feature developers could prevent the mistakes of unintentional step copying during creating new subsequences using the copy-paste method.

The default value for this settings would be AllowAllCallers, but developer would be able to define the condition as they wish (function window f(x))

Hi,

The best would be to draw/paint the feature I'm proposing. However, it would take not so small amount of time, so I decided, regrettably, to write about it.

I wrote the word regrettably because visualised description of the target feature would be very much more attractive than words. Anyway... Back to the point.

The description is as simple as in subject: to allow to change the colour of the background of each step (separately).

Could you imagine how much the readability of the sequence could be improved with this feature? I think that would improve it a lot.

Mainly this feature could be enabled during coding and debugging as during these activities the developers have the problem with readability especially when the sequence is long and the whole project is big and long in time. It could be set to off on when the sequence will be on the shop floor, nevertheless, even in the operator mode this feature could deliver some 'tracing' benefits.

Developers could easily group block of steps and in very natural way - just to color the background of the steps - create a visual 

Reading colors is faster, easier, more intuitive than reading the structures (indent, nested calls). OK it is  - let call it  - one dimensional and it looks flat but it would add another degree of freedom in classifying/grouping the steps improving and speeding up overall readability.

The place (yellow) where this feature (just colour) can be controlled from:

Hi,

As in the subject.

Now to create a session from the TS two arguments are needed:

--device name (address or alias), and

--session number.

However, comparing to LV, LV needs only one of them, the device name. Why two of them have to be different?

It can happen that session number doesn't exist because the session itself doesn't exist yet. So why this field is made mandatory?

Usually, I put any random number there (0-9) and everything works, but it is not a nice coding style.

I think the Session Number field should be set as not mandatory.

I am trying to edit step variable properties from step to step.

I edit Step.Foo.Bar.Bing.A in the first step.

I click to the next step, it also has Step.Foo.Bar.Bing.A in it, so I edit that value.

I click to the next step, it doesn't have that variable, so I see nothing.

Click to the next step.  @#$%@#$.  Expand Foo.  Expand Bar.  Expand Bing.  Edit variable A

Click to next step.  Still expanded.  Edit variable A

click to next step.  No variable matching that value.

Click to next step.  @#$%@#$%.  Expand Foo.  Expand Bar.  Expand Bing.  Edit variable A

This constant Expand the tree is really annoying.  I'd love to be able to set an attribute of a container to say "always expand this completely whenever It shows up", or a sequence editor wide configuration of "always expand all properties when you browse to them" which would work fine unless you have "show hidden properties" enabled, and then you have the whole Step.TS.* tree visible, so maybe a "expand all custom properties" or "expand all non-hidden properties" or something like that.  Or maybe a way to click on the "+" expanding symbol for that node in the property browser that would completely expand that node