Libraries and classes both use VI.Library.Path property
It creates the following unexpected behaviours:
- If you run the plugin and specify library but it is a class, there will be no error and it will bring up the class folder
- If you run the plugin and specify class but it is a library, there will be no error and it will bring up the library folder
- If you run the plugin and specify library but the library contains a class that contains the VI, there will be no error and it will bring up the CLASS folder
I need to separate out libraries and classes in Get Paths from Ref.vi and work out a way of seeing if it is a library or a class.
Libraries and classes both use VI.Library.Path property
It creates the following unexpected behaviours:
I need to separate out libraries and classes in Get Paths from Ref.vi and work out a way of seeing if it is a library or a class.