NI TestStand Idea Exchange

Let's say we have a parameter to a subsequence of a named type, and we want to create a so-named Local or FileGlobal with the same type.

One way to do this with our current workflow is to:

• Type the same property name in the parameter value
• Right-click the parameter
• Click on "Create Locals.whatever"
• mouse over the types menu
• Glance through most of the types, select the custom type

I'm proposing a simpler workflow for cases when you just want to duplicate or "clone" the property with the same name and type in Locals or FileGlobals:

• Right-click the empty parameter value
• Select "Create Locals.whatever" or "Create FileGlobals.whatever"

The respective menu options would appear if the so-named variable does not already exist.

The subproperty is created in the Locals or FileGlobals with the same type as the parameter.

Hi there,

When using the Find/Replace dialog in TestStand, it would be nice to have a checkbox under "Elements to Search" that allows the user to choose whether or not to include sequence file attributes in the the results. I guess I could put together a regex to accomplish what I need to, but a checkbox would be nice.

Why am I asking for this?

I'm used to quickly working my way through find results by using the CTRL+G / CTRL+Shift+G shortcuts. When I hit one of these attributes there's about a 4 second delay before the sequence file attributes dialog opens. This is super annoying in the workflow of the find results, and the vast majority of the time I'm not interested in searching the ignored Sequence Analyzer messages.

Thanks,

Mr. Jim

Problem description:

The parameters out of the step settings window and the called subsequence are not linked. If you delete any parameter out of the middle of the parameter list and the calling sequence use the "default" flag for this parameter(s), this default flag(s) will be shifted to the next parameter in the list and the original value will be overwritten. To reproduce this issue:

1. Create a test sequence
2. Create a subsequence and add six parameters (type does not matter)
3. Insert "Sequence call" in the Mainsequence and configure it to the previous created subsequence
4. In the "StepSettings" window configure the parameters of the called sequence. Parameter 1+2 with any value. Parameter 3+4 with default checkbox. Parameter 5+6 with any value
5. Save your work
6. Open the subsequence and delete the parameter 3+4 (these two that are configured with "default" in the calling sequence")
7. Go back to the MainSequence and click on the sequence call of the subsequence (reload option is visible in the step settings window)
8. click on the blinking red reload button

You can see that the name of parameters you have deleted in the subsequence disappear, but the "default" flag(s) are shifted to the parameters 5+6 and the previous configured values were overwritten. If you delete any parameter that is configured without the default flag the deletion works fine. 

Problem: If you want to delete a parameter that is used in many subsequences by searching for it and delete it directly out of searchResult window, you cannot guarantee that your sequence is running without any problems

Idea: Add a "checkup function" on the "reload" module in the stepSettings menu that all parameters are checked by name and value before any values will be overwritten. This checkup has to be done on each change of the called subsequence

I would like to request to add the possibility to start Tool (Menu>Tools) from Quick Drop. E.g. I would like to create a tool which sets selected steps to overwrite reporting option and run this tool with Quick Drop.

I would like to see the possibility to add Tools (Menu > Tools) to Toolbars. See the recording below:

As you can see from Tools section I can select only "Customize". It could be great to have the ability to use custom tools when customizing toolbars and menus.

Please include Wait(x mSec) or Delay(x mSec) operation as one of the method in sequence context, so that this can be used in Function Statement step, Post action of any step to force the step to wait for few mSec after completing it's operation. This is to avoid explicit inclusion of Wait step and majorly useful during looping a step and provide delay between each iteration.