NI TestStand Idea Exchange

A Rendezvous has a fixed size. If size needs to be changed the rendezvous must first be destroyed and created again which results in an error for objects already waiting for the rendezvous. I suggest the size of the rendezvous might be incremented/decremented dynamically as in LabVIEW.

Hi,

Exactly like in the subject.

Now property loader can cope with the first sheet only. It would be good if it can cope with multiple sheets.

Kamil

Right now in "On Run-Time Error" combo box in Execution tab in Station option we have the option as below:

I think another one shall be added which would be Retry. At some ocassions, it'd be good if TestStand, in case of an error, could retry to execute the step for second - or even third or forth - time, by default.

In a custom UI I currently need to have two AxSequenceView controls to display sequences:

1. Connected to the AxSequenceFileViewMgr. This shows the static view of the sequence file and is where you can attach the debug context menu to loop selected steps etc.
2. Connected to the AxExecutionViewMgr. This shows exactly the same view of the sequence file during execution, with just an additional "Status" column with the result status of each executed step. You can toggle a breakpoint by clicking in the margin but can not select steps or operate a debug context menu here.

Of course I could display both views in the UI but this feels illogical for the user, so I prefer to show only one and switch between them according to context. However this presents problems:

1. As this post (not one of mine!) says, you have to display the SequenceFileViewMgr view after loading a program because the Execution View would be blank, and then switch to the Execution View when the program is running.
2. You have to switch back to the Sequence File view when the program ends in order to re-enable the debug context menu. This means that the step statuses disappear before the user has a chance to look at them in detail. It also means that the new view is not aligned to the execution view (i.e. the first visible step is different) - this may be solvable with a lot of programming but I haven't worked out how!.

It feels to me that it would be better for the API to provide a single view of the sequence file that has the debug facilities available, with a status column that is blank (and gets reblanked at the start of every execution). My UI code would be considerably simplified!

Hi,

As in the subject: add ability to sign the sequence with the digital signature.

It would be good in this feature will be able to access the certificates stored not only in Windows containers, as it is done in LV now, but the containers located on external carriers USB cards, card readers.

Hi,

Exactly as in the subject.

There is a need to add the explicit, text-based, if-then-elseif-else syntax to the list of command allowable in the statements and function definitions.

I know I can use C++ style of the if-then-else-elseif syntax, but in more nested expresions the readibility of it gets worse and worse very quickly.

Having this functionality would simplyfy the readibility of the statements.

My original thought was to have a context menu appear when you right click the response box of the popup so that you could then click 'Paste' but having a right click paste like in a Linux console would be even better since it is pretty rare that someone would be copyiing data from the input box. The feature could be selectable in the Property Browser (e.g., "RespRightClick" with two options--"Enable" and a toggle between "Paste" and "ContextMenu") or maybe just check boxes on the "Options" tab.

Could some distinction be made between a button timeout and a button press, on a Message Popup step? Step.Result.ButtonHit returns the same value regardless. Perhaps return a negative value for a timeout, and a positive one for a button press?

Thanks 

Bruce

Background --

When I have a step in a sequence file, and I change the Load Option of the step, and I go to Sequence File Properties and change the global Load Option to something other than "use step load option", I get red exclamation marks next to my load options on my steps to let me know that that value is overridden by the global sequence file option.

HOWEVER

if I look at the Result Recording Option, I see the step result recording option configured for that step.  But, that can be overridden by the Sequence Properties  -> "Disable Result Recording for All Steps".  I would expect that I would get a similar red exclamation mark next to the result recording option in my step properties configuration page to let me know that that value is overridden by the sequence option.  Possibly also update the settings column to include "result recording disabled" message like it would if I flagged just that step option to disable result recording (although I am a little more on the fence about this part)

On a similar but different topic, it is horribly hard to understand whether a sequence itself has configured to disable results recording.  I need to go through each sequence individually and look at the sequence properties.  Adding a settings column for the sequence list view would be nice.