To summarize, you want to think about using OOP when You have code that you want to reuse but can't fit it into a traditional subVI You have a wire or a terminal and you want it to switch between type definitions You want other people to be able to use your code without modifying your VIs You want to constrain the developer in what they can do with the data on your wires (eg you can prevent them from prematurely releasing your queue) You want to be able to open your current config files with future versions of code. You'll need LapDog to open the LapDog read example where I extend the LapDog API to add an "anything to string" function.

San Diego LabVIEW Users

To summarize, you want to think about using OOP when

You have code that you want to reuse but can't fit it into a traditional subVI
You have a wire or a terminal and you want it to switch between type definitions
You want other people to be able to use your code without modifying your VIs
You want to constrain the developer in what they can do with the data on your wires (eg you can prevent them from prematurely releasing your queue)
You want to be able to open your current config files with future versions of code.

You'll need LapDog to open the LapDog read example where I extend the LapDog API to add an "anything to string" function.

CLED (2016)