Adding Relative Path Support into Modules

[AdamH-KarmanSystima]

Hoping to reach the devs with this really simple addition.

It's super handy that TestStand supports relative paths when selecting the module to call (I.E. VI Path) inside a step. However, relative paths as expressions into those modules are not supported. Why not?

As an example application, it'd be really handy if I could use just pass "MyOutputData.txt" as a Path input into a LabVIEW module. Right now, I have to use something like: RunState.Report.TemporaryFileLocation + "/" + "MyOutputData.txt".

Obviously, absolute paths wouldn't be altered, but having TestStand assume the first portion of that allows me to create files or even subdirectories with files local to that report directory. LabVIEW would still receive a valid directory as it's input parameter, TestStand would just take over evaluating the full path rather than having to write dynamic expressions in my module step.

Maybe I'm not the only one wishing for this easy feature?

[Anand_Jain]

There is some potential value with this idea but also some potential issues. Can you post in the TS idea exchange to have better visibility and discussion?

NI TestStand Idea Exchange - NI Community

Note: You can pass a relative path and obtain the absolute path in your code module with a call to TS's API - FindFileEx

Regards, 

Anand Jain

NI