NI TestStand Idea Exchange

Let's say I'm building a fairly long compound expression that has some repeated parameters - I would like a way to specify (without creating additional locals) a variable/macro for use just within that expression.

For example, instead of:

Locals.CommandLine = "cmd /c C:\some path\that\is\reused"
Locals.CommandLine += " /path C:\some path\that\is\reused"

I could specify:

#pathmacro "C:\some path\that\is\reused"
Locals.CommandLine = "cmd /c " + pathmacro
Locals.CommandLine += " /path " + pathmacro

The idea being that with this I only need to update the macros in one place in a long expression.

This is a simple example, but hopefully you can see why this would be useful and why I wouldn't want to create lots of locals when the values are required only within the expression.

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.