09-27-2023 06:42 PM
Without the comparison and case structure (i.e. just using the path out of the invoke node), it works OK when Path In is any of:
but not when Path In is:
Does this seem sensible to anybody?
Solved! Go to Solution.
09-28-2023 01:17 AM
Hi Paul,
Replace the BasePath with a paths constant "<>:\" and start testing 🙂
Have fun and let us know the result.
This Invoke node seems a bit idiosyncratic to me. I have made a note sometime ago, that it seems to work well with an idiodic BasePath. Something like "<>:\" or "<abc>:\
I never examined it in detail.
09-28-2023 09:44 AM
@Martin_Henz wrote:
Hi Paul,
Replace the BasePath with a paths constant "<>:\" and start testing 🙂
Have fun and let us know the result.
This Invoke node seems a bit idiosyncratic to me. I have made a note sometime ago, that it seems to work well with an idiodic BasePath. Something like "<>:\" or "<abc>:\
I never examined it in detail.
Using either "<>:\" or "<abc>:\" causes it to always give the wrong answer.
09-28-2023 12:03 PM
When using the VI those appear to have "standard" property node appearances, it looks like those are both private methods not intended to be used by users. I can find no help files, and the two Wiki entries for them both are light on details except for them being private:
https://labviewwiki.org/wiki/LVTarget_class
https://labviewwiki.org/wiki/LVTarget_class/Convert_to_Symbolic_Or_Relative_Path_method
So I would speculate that the actual reason is "because it needs to work like that for the internal NI methods that use this to work right".
09-29-2023 12:17 AM - edited 09-29-2023 12:19 AM
Kyle97330 might be correct.
It seems to work perfect here on my PC (Windows 11, 32 bit labview 2021 - 21.0.1f2)
I have attached a modified VI using "<>:\" for the BasePath and removed case structure. The defaults of "Path In", "Symbolic Path" show what I see after execution of this VI.
Path In:
C:\Program Files (x86)\National Instruments\LabVIEW 2021\vi.lib\Utility\Sync.vim
Symbolic Path:
<vilib>:\Utility\Sync.vim