09-27-2013 12:12 PM
I'm curious if anyone has tips for managing Labview classes that change inheritance often. For example, i often make a generic class that encapsulates the functionality of a piece of hardware, lets say a flowmeter. In one project i may want this to inherit from the Actor Framework so that i have the benefits of this system, however, in another project i may not want this inheritance, on a crio for example. Maybe i'm understanding it wrong, but i would have to make a new copy of the flow meter files on my hard drive in order to change inheritance for one project and not effect the other.
If i change the inheritance in one project this essentially breaks my other project. However, if i want to change the functionality of the generic flow meter object, i then have to update every file location. Really the only thing i could maybe think of would be to check the class out of a repository and then push changes to it that way.
Any suggestions would be great or like i said maybe i'm just not understanding it correctly.
09-30-2013 08:49 AM
Hey,
Changing the inheritance will mess up your other projects. Without knowing your code, the two recommendations I have is you can either make the code more generic or make a wrapper for the two objects you are inheriting from. Also, you can always copy the file to a new location and then change the inheritance.