I'd like to put my interface classes in a separate packed library which I add as an item in an implementation project. The ultimate goal would be to realize a plugin architecture similar to https://forums.ni.com/t5/Phoenix-LabVIEW-User-Group-PLUG/Plug-in-Architecture-using-Classes-and-Pack...
but with Goop classes.
Unfortunately when I face several errors:
- When creating a new class inheriting from a parent class in a lvlibp: The Parent_Create.vi and Parent_New.vi are not "found" so in Child_Create.vi and Child_New.vi the Goop template VIs are used instead and have to be replaced manually.
- When creating an override method I get an error 1063 (screenshot attached), and the VI will be only partially created (only ref and error FP elements, default blockdiagramm). That means that the overriding method has basically to be implemented from scratch manually.
Tested this with LabVIEW version 2012 and 2017
So the question is:
Is there a way to make the goop class and vi creation tools work like it ususally does without the need for those many manual operations?
