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.
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.
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.
Often times a sequence file ends up containing dozens (or even hundreds) of sequences. Currently they all show up in the sequence editor Sequence Window as a flat list. It sure would be nice to view them organized in folders so that, for instance, all my sequences dealing with Rs485 communications or whatever could be group together in a "folder" called "RS485". Also it would be great if there was a displayable property for each sequence showing the date/time last modified. Then you could sort the list on that and see which sequences have changed. (really helpful if you have multiple guys who might be making changes.)
I think it'd be good if the Requirements property (in step properties) would be able to recognise url like http:// https:// svn:// notes:// etc.
Then we could directly link the step to the requirement system which could save a lot of hassle with changes tracking.
For now it is a plain text only.
It would be nice to make Sequences public or private within a SequnenceFile.
With this you where able to make powerful SequenceFiles librarys. The biggest advantage of this
is you can show the consumer of the library only the "important" public sequences. The
private ones where invisible. This will help to avoid errors.
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.
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 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.
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.
Hello all TestStand fans,
For my recent project i had to modify the frontEnd callback.
=> According to the TestStand help, the only path where this file can be created is in TestStand default path or in the corresponding user path.
.... But no where else !!!!
It would be nice to be abble to configure the frontEndCallback path in the configure options !
=> Doing so, the path of this callback could be placed everywhere ! (In the configuration path would be nice !)
=> Doing so, it would be possible to create a frontendcallback for each configuration !
I am a TestStand developper, a NI partner, not a TestStand end user.
My work is to provide custom sequencer for my customer.
On my computer i had to manage many different sequencer !
I think that if it is impossible to do so, today, is because this callback is loaded before the "Station configuration" is loaded ?
My ideas should be applyed to all global files ...
Doing so, will also simplify the deployement process !!!!
=> A single path copy ... is quite easyer as a complicate deployment process !
Thanks for your help.
If you have lot of code between an if, else, end statement steps (and other flow control structures for, foreach, while, and etc.), it would be nice to roll all that up so you can see more of the flow of the sequence. This will also help to know what steps are in those structures in large sequences. TestStand already has some code folding in the sequence, so this is an expansion of this. Many text and code editors have this feature and it would be a great feature for TestStand.
Would be great to have Local of type Image. Right now image is saved and retirved for analysis or convert to array to use in other steps.
Something similar like the idea ;
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.