When working with multiple long sequences it would be nice to bookmark locations making it easy to find where you were previously working. The bookmark could be line highlighting or an icon on the left gutter. Bookmarks would be saved with sequence. Multiple colors or icon would be available.
It would be nice if the Step Settings for a Sequence Call step's Module tab would also list the calling sequences comments field and the parameter comments in addition to the prototype information. This would allow sequence calls to easily present information on the expected use of the sequence, along with parameter information (ranges, default options, etc) that would be useful to the developer. I've created a simple mockup of what I'd like to see here:
By adding these features, sequences can contain their own 'help' information which would allow the developer to configure the call without having to leave the step module dialog.
It would be great to have the ability to create an independent TestStand configuration that is valid in a workspace context. That would allow project specific search directories, StationGlobals an several other configuration items you normally don't want to share across projects on the same test station.
I LOVE the autocomplete feature within any of the formula windows. Start typing Locals.F, and it allows you to autocomplete to Locals.Foo.
However, if you have Locals.Foo1, Locals.Foo2, Locals.Foo3, etc, you need to keep typing until you get enough to uniquely match the one you want, or start using the arrow keys in the list (or select with a mouse).
The problem is that if you just type Locals.F, the list of items that shows up is the entire list of Locals.*, in the order they are in Locals.* In reality, once I've typed Locals.F, I should only get the locals variables that start with F, so I don't need to down arrow through all the other Locals.Bar1, Locals.Bar2 that are inbetween Locals.Foo1 and Locals.Foo2 (because for some weird reason I really want the order of my locals variables to be Foo1, Bar1, Bar2, Foo2, Foo3).
So, let's restrict the autocomplete function to only show the items that match what I have already typed, or at least regroup the matching variables at the top of the list so they are easier to select from.
Even better would be to have it context aware. If the formula I am typing is "Locals.MyNumber = 3.1415 * Locals.F", and Locals.Foo1 is a string, Locals.Foo2 is an array of booleans, and Locals.Foo3 is a number, then it should skip over Locals.Foo1 and Foo2 because the context requires a number. Foo1, Foo2, Foo3 should all be in the list of items to choose from if I want to arrow up or down in the list (or use a mouse to select), but Foo3 should be the "defaulted" item that is used if I just hit enter after Locals.F.
I have a sequence file that contains hundreds of sequences. It would be nice to be able to logically group and organize these sequences, such as in a tree control with virtual directories (hierarchy), instead of them being in a single long list.
Some test sequencing tools incorporate the idea of configuration based variant handling, where you could define different test variants (e.g. testing at ambient temperature, hot, cold), each variant having it's own set of test limits.
Individual test steps can then be assigned to the previously defined variants. By chossing the desired test variant, the according steps will be executed without having the need to implement additional logic within the sequence.
It would be helpful to be able to change the font colors that are displayed for steps in the sequence editor. This would allow users to identify steps quicker for more efficient editing and debugging.
The MOST annoying part of working with TestStand is the fact that the developer has to re-enter e-v-e-r-y bloody value for a given parameter when the prototype changes in a LabVIEW VI.
As a sister idea to this one, what is more annoying is the fact that when the container exists for a previous step and is already populated with all the values that you want to repeat elsewhere, TestStand does not allow you to copy and replace a parameter! Unless there a non-obvious way of doing this (I will attempt a few unorthodox ways to get this done). If so, it should be an obvious method and not something that requires contortions to accomplish a simple copy & paste.
Even if the copy & paste could be done from within the parameters, ie: ability to select multiple values and paste them all into the parameter. This is such a basic feature is most or all programming languages and applications that I cannot believe it does not exist in TestStand.
In this particular case, the values are from Locals. variables. And there are lots of them; between two parameters, over 300!!
Let's get on with the times!! Improve the copy & paste feature, even for an ultra basic request like the one Ray Farmer requested in 2011.. See this link:
The menu to create a new variable (right click on variable in an expression edit control and select Create "VariableName") contains all the data types you can use for the variable, however, in the LabVIEW Panel (and other similar panels or dialogs) there is enough context information about the variable to suggest a data type, for example, if the variable is in a control of type Double we know we should create a Numeric variable. TestStand should add the contextual suggestions to the top of the context menu and bold them so that I can more quickly select the data type I want most of the times, then have a separator and put the normal menu so if I don't want that data type for some reason I can still choose the other data types (see attached image).
It would be nice to be able to create a new sequence from highlighting steps in a sequence and performing a right mouse click, "Create New Sequence...", this would be a kin to Create SubVI in LabVIEW.
This action could display a dialog to give possible options such as, to copy the Setup and/or Cleanup group, Create in a New SequenceFile or in Current SequenceFile, the option to Move or Copy highlighted Steps. It could also include creating any locals and /or FileGlobals (if creating in a new SequenceFile) used by those highlight steps.
How many of you would benefit from the addition of a feature similar to LabVIEW's Quick Drop?
The functionality that initially comes to mind would be typing to search for your desired step type or step template and dropping it into the sequence you are developing. Please add comments for any additional functionality you might like to see in a TestStand step Quick Drop (for example, you may want TestStand to automatically navigate to the Step Properties of a step after it is dropped from Quick Drop).
Please also add comments for any other situations/scenarios (outside of adding steps to a sequence) where you might benefit from a Quick Drop-like functionality. Thank you.
During development of sequences I often do "trivial" changes in order to check parts of the sequence that I do not want to save afterwards (e.g set Run Modes of steps to Skip). It would be very helpful to see the last changes that can be undone before clicking the Undo-Button arrow (the same applies for the Redo Button of course). This feature would have two major advantages, since one could...
This is implemeted in Microsoft Office programs for example (see screenshot from MS Excel) and I use it there pretty often.
It would be nice to beable to define a variable as constant.This could apply to Locals, FileGlobals, StationGlobals.
Once set mark it so as to be easily identifible as a Const.
The API would also need to include either a Property or Method so that one could determine if a variable is a Constant.
I think this Thread should be placed here.
The aim of this is that users can create the same powerful steps like that once which comes from NI.
Biggest enhancement of this would be that i can get rid of the "edit" - button and there is no floating panel
The second enhancement is that i may use drag and drop between the edit and variable panel (if this is neccessary).
Like Manooch_H I am interrested in comments, too
When you set the Post Action On Pass | On Fail in a step to use Call sequence, the only ways to pass data to this sequence is either use some sort of Global (StationGlobals / FileGlobals) or use Locals with the setting "Propagate to SubSequence".
There should be a cleaner way and that is to beable to pass parameters as you do with SequenceCall step type.
It would be nice when entering in the Find: control to beable to pop open the Variable dialog (as in the expression editor) to select variable names. It could be linked to the Limit Search to: control. Like wise on the Replace control when that window appears.
I know you have that drop down facility on this control but that only remembers what you have previously entered.
I find myself creating arrays alot and I usually have the array already made in excel or note pad or another type of file in which the list might be around 20 or more entries. Now in the past I've come up with a simple way to import the arrayed data from a file, but however i don't believe everyone is doing this and generally I don't need the file in which gets imported (usually a simpler version of the master). So i suggest could we add the support to copy from excel or from notepad and paste special into an array.
This idea might not be the best, fastest, or easiest way to import arrays from other programs, but the idea would be to find an easy way to import arrays.
Having the ability to have line numbers for all steps in the left hand gutter would help in troubleshooting, code reviews, and any time when communicating about a sequence. There seems to be a gutter there already, so adding there seems to be a place for them already. Error messages can also post the line number too.
The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.