While object-oriented programming in LabVIEW is not an extension of VI Server (LVOOP and VI Server use separate class hierarchies), using property and invoke nodes means that you already leverage inheritance in your LabVIEW code. We often use a property node to programmatically change properties through VI Server. If you ever use property or invoke nodes, the concept of class inheritance might sound familiar. Pillar One: Inheritance – Classes can have parent/child relationships. Look for posts on the other two principles (encapsulation and polymorphism) sometime soon. In this post, I dissect one of the three foundational principles of object-oriented programming in the context of LabVIEW: inheritance. When a class does too many things, the class likely requires frequent modification, probably loses reusability, and generally fails to provide the benefits of object-oriented programming. Class– A LabVIEW class is simply a unique type of library that always contains one private data cluster (sometimes we refer to classes as abstractions or types)Ī class takes care of its own business and, ideally, this business is limited in scope.Method– A LabVIEW method is nothing more than a VI belonging to a class library.Object– A LabVIEW object is just a cluster with special abilities (a private data cluster).Mix these concepts together, give them a little stir and… BOOM!Ī class is simply an objectand a set of methodsthat act upon it. Translating into LabVIEW terms: As a regular G developer, you probably encounter clusters, libraries, type definitions, property nodes, and polymorphic VIs on a daily basis. Object-oriented programming is not magic-it is a programming style built for modularity, and maintainability. If you do not currently leverage object-oriented programming techniques in your LabVIEW code (believe it or not) you likely know more than enough to get started.

Invoke node labview