LabVIEW
Project Items - LVLibp class in scripting
Hello,
I am trying to do some scripting with lvlibp in my project, but it seems there is no way to cast LVLibp type to more specific class and list classes and members that are inside:
Similar code works for libraries.
Is there way around this?
Which node gives an error, and what is the error?
If you get an array from OwnedItems[] , I'd start by listing the class names of the members.
Search LabVIEW like a graph! I want to get reference to class inside packed library.
For normal source code library it forks without problems:
But for packed library cast to Library class fails, I can not find LVLibp class to cast it correctly.
But what class is it that reference? If you get the ClassName property, you know what you can to cast that reference to. A probe gives this info too, without any programming.
Hi pawhan,
"Owned Items[]" is a property of class "ProjectItem", so for your case, you wouldn't need to cast your refnum to a more specific class:
... but the fact that you cannot cast it to a Library is surely an oversight from NI because you can easily get it as a Library like this:
...or like this:
...you can even type cast it directly and use Library properties without problem:
So you could report this behavior as a bug to NI, because the LVLibp refnum IS a library.
As a side note: "LVLibp" is not a VI Server class, it is a type string as returned by property "Type String" of class "ProjectItem".
This is sometimes correlated, like VI Server class "Library" has the Type String "Library", or "LVClass" has the Type String "LVClassLibrary", but this is not the case for most items. There are way more Type Strings than classes in the Project Item hierarchy.
Regards,
Raphaël.
@_Y_ wrote:
wiebe@CARYA wrote:
But what class is it that reference? If you get the ClassName property, you know what you can to cast that reference to. A probe gives this info too, without any programming.
I have the same problem. The ClassName property returns LVLibp and I cannot find corresponding constant for using with To More Specific Class
That's why the dependencies (including the parent) shouldn't be compiled in the PPL when the child is packed.
@paul_a_cardinale wrote:
@_Y_ wrote:
wiebe@CARYA wrote:
But what class is it that reference? If you get the ClassName property, you know what you can to cast that reference to. A probe gives this info too, without any programming.
I have the same problem. The ClassName property returns LVLibp and I cannot find corresponding constant for using with To More Specific Class
As far as I can tell, the "LVLIbp" class is not exposed.
Only 7 class names contain the characters "Lib":
- CallLibrary
- LVClassLibrary
- Library
- LibraryData
- StatechartLibrary
- XControlLibrary
- XNodeLibrary
A packed library is a library.
Not sure why you'd need this though.
