You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been having some trouble with the 'bitfile path on target relative to root' field that's on the cRIO configuration.
It says 'relative to /home/lvuser' but when I put the file name in the error message indicates that it tries to load it from the root directory.
Here's a snippet to illustrate the problem:
I also can't really edit the bitfile path on target field because LabVIEW 'helpfully' converts my path to windows style. Maybe we should use a string here.
The text was updated successfully, but these errors were encountered:
Yeah, the utter worthlessness of the path control when working on a cross-target application is a sore spot with us. We've done some work on other modules (TDMS included) to swap in a string or a path control depending on which target is being used. There is also some ugly string parsing work put in previously to "de-correct" the path. @becega might be able to comment as to where that lived.
I've been having some trouble with the 'bitfile path on target relative to root' field that's on the cRIO configuration.
It says 'relative to /home/lvuser' but when I put the file name in the error message indicates that it tries to load it from the root directory.
Here's a snippet to illustrate the problem:
I also can't really edit the bitfile path on target field because LabVIEW 'helpfully' converts my path to windows style. Maybe we should use a string here.
The text was updated successfully, but these errors were encountered: