How to use the same vi.lib class in multiple PPLs as a the same class?

[bienieck]

I’d like to ask how to ensure that the same class from vi.lib, which is embedded into different PPLs, is treated as the same class even though it originates from separate PPLs.

Specifically, I’d like to know if it’s possible to achieve this without creating a separate PPL for the shared class. For example, is there a way to forcibly enforce this, through some special type casting methods?

Any insights, tips, or examples would be highly appreciated!

[bienieck]

Perhaps something like LabVIEW Object to VCluster or Cluster to LabVIEW Object from OpenG could help here? Is it even working with PPLs? (By the way, I think there might be an issue with the VI Description in one of these VIs. Also, the link http://www.labviewwiki.org/LVClass_Data_Storage_Format used as a reference is no longer working.)

[bienieck]

Ok, I figured something out, but I think it’s more of a last resort. Having a separate PPL with a common resource seems to be a better solution.

[raphschru]

Hi Michał,

I've had the same approach here:

https://forums.ni.com/t5/LabVIEW/dynamic-call-VI-outside-a-PPL-with-a-class-and-in-another/m-p/43135...

Otherwise yeah, put your class in a "common PPL" and refer to this one from your other PPLs.

Regards,

Raphaël.

[avogadro5]

In the PPL build spec, if you set the destination for a class as the support folder, the class will not be renamed and the links inside the PPL will be to the original class name. If you load that PPL into an app that already has that class loaded the ones in the PPL support folder won't be loaded at all and you can delete them if you feel safe assuming the caller app will have them already.