Execution Globals

[StephenGerads]

globals scoped to an execution

currently I use RunState.Root.FileGlobals as execution globals

but adding a custom global there normally requires modification of the model

[Josh_W]

This functionality already exists in TestStand:

RunTimeVariables Property

Since these variables only exist at runtime, you'd need to create them programmatically by calling the API. To access them you could just use the expression Runstate.Execution.RunTimeVariables.<VariableName>.

[StephenGerads]

It would be nice if the execution variables were not only runtime variables, so they would could be created normally (rather than programmatically) and browsed to normally.

[AllenP]

An execution only exists at runtime.  How could they exist outside of that?

[StephenGerads]

Lots of variables are visible outside of runtime in the expression brower during editing, and it is very helpful that they are.

[Bluegraf]

Not only these RunTimeVariables are only creatable via the API, they are also terribly bad to see.

The same is valid for TemporaryGlobals which are even tedious to set and get (locals.whatever = TemporaryGlobals.GetValBool("Flag") ... hope I recalled the expression right, have no TS around here).

But worst of all is that the above are only mentioned somewhere deeeeep in the documentation. If you do not know they exist you are not likely to stumble over them.

[WireWeaver]

I'm declining this idea due to lack of community support. Also, it's still unclear to me what is different about this idea from TemporaryGlobals