From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Wouldn't be nice to beable to define one's own set of Expression Functions.
This seems to be the one area of TestStand that cannot be customised.
eg.
Locals.name = NameOf(Step), Locals.IsValid = DoSomethingNotDefinedByDefaultFunction(Locals.name),.....(carry on with expression)
Regards
Ray Farmer
Defined in a similar way custom step types are defiend. I see this as a way of using the code defined in a custom steps type but being able to use it in an expression.
It would be like having a custom step or a code module which has a pre-expression and post expression but it's all done in the Expression control.
I had to think about this one for a bit, but on second-look I could see that as a great way of cleaning up some very ugly expressions I've encountered/written over the years... especially the sort people are obliged to make when tweaking the sequence view in an operator interface or the ModuleDescription within a custom steptype.
It could be like definining mini VB scripts/ stored proceedures within TS... but with the potential to make use of the API / existing expressions.