LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why Do I Need This Case Structure

Solved!
Go to solution

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:

  • instr.lib
  • Anything under instr.lib
  • user.lib
  • Anything under user.lib
  • vi.lib

but not when Path In is:

  • Anything under vi.lib

Does this seem sensible to anybody?

0 Kudos
Message 1 of 5
(425 Views)

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.

0 Kudos
Message 2 of 5
(369 Views)
Solution
Accepted by topic author paul_a_cardinale

@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.

0 Kudos
Message 3 of 5
(312 Views)

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".

0 Kudos
Message 4 of 5
(288 Views)

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

 

 

0 Kudos
Message 5 of 5
(245 Views)