VI ownership mess when libraries/classes are involved

[calvintiger]

I am having issues with the way that libraries or classes claim ownership of a VI.

Let's say that I have a very simple VI that doesn't depend on any other file (just a mathscript node with inputs and outputs).
I have added this VI to a class.

Now, the VI seems to be claimed by this class - meaning that a whole lot of files that I don't need get loaded whenever I add this VI to the Block diagram of another program (unrelated to the class).

How can I solve this issue ? Do I have to remove the VI from the class ? Cannot a VI be claimed by different classes, or ideally, is it possible to let the class know that the VI belongs to it without affecting the VI ?

[Broken_Arrow]

There's no reason why you can't place that VI in a new VI. Have you saved the VI to a new location outside of the current project?

Can you post the VI? Let's see if one of us can load the VI.

[Mark_Yedinak]

If you are trying to use only one VI (method) of a class without the rest of the class it sounds like this should not be part of a class. Perhaps you are not defining your classes properly. Classes and their members should go together quite naturally. If you have shared VIs that you want to reuse you can always define a reuse library of VIs.

[Norbert_B]

I am confident that this is expected behavior. I think this is the "overhead" you require for name spacing and such.

Norbert