Hi All,
Unfortunately, TestStands Help for omitting Optional Parameters covers everything BUT TestStand on this subject!
When using a Function call in a step, I'm wondering what the best practice is for handing optional inputs and outputs. Because leaving it blank is not an option, I've found that instead of creating a dummy local variables; i.e., Nothing, 0, "", or an equivalent value type that matches the parameter type seems to work okay. Effectively as long as the statement evaluates properly, you're good.
For instance, the FindFile () function has optional inputs that aren't at the end and can't be left blank:
Boolean FindFile(String fileToFind, Boolean useCurSeqFileDir = True, [String PathToFile], Number promptFlag = 1, Number searchFlag = 1, [Out] [Boolean canceled], Boolean isCommand = False)
So the following: FindFile(Locals.Comp.DataFilePath, False, "", 3, 3, 0, False) works just fine during execution.
That said, is there any potential downside to doing the call this way?