09-13-2023 01:07 PM
Thanks for the conceptual idea
09-14-2023 03:06 AM
@Melchizedek24 wrote:
In the above mentioned example, innstead of 3 shift registers, can we club them into a songle cluster and pass down as a single line? would it look good if it is used as a cluster?
Yes, that is done a lot.
I'd prefer a class for each 'cluster' of items that fit together. That way, I can enforce the encapsulation of the clustered data, and have all methods on the cluster contained in the class.
But don't do OO on a CLD unless you're very comfortable with it.
A cluster will do.
You probably want to make it a type def (right from the start). There will probably be a few cases (assuming you're doing a state machine of some sort) with constants of the cluster, and a type def will update them automatically.
09-15-2023 09:06 AM
Thanks for your valuable feedback.
I am sorry that i am not able to follow one of your statements: "Dont do OO on a CLD". Can you enlighten me what is OO please?
09-15-2023 11:57 AM
OO = Object Oriented, i.e. using a LabVIEW class (.lvclass) file instead of a cluster.
While LabVIEW classes can be great, they shouldn't be needed on the level of coding a CLD will ask for.