Best Practices when handling lots of GUI elements and big data cluster

[Taggart]

Control references are very powerful, but that power comes at the expense of readability hence their use should be always approached with some amount of caution and deliberation.

[AlexElb]

Hello Everybody,

as this is more a open question, I won't mark any post as a solution, but nevertheless thank you all very much for you thoughts and tipps! I did rethink a few of my designs and I am still thinking about how to make things work easily and nice and probably will post here from time to time again. As now 🙂

Lets say in a module I start to process a picture from an IR Camera (2D DBL Array). I have one MHL case for that, because it receives the picture thorugh a broadcast of another module. Now the modules data cluster holds the settings of the module, right? So in that big cluster it is stored, whether the picture should me turned arount (right or left, how many times?), mirrowed (x- or y axis?), unit conversion (C or F?) and I could think of 10 more easily...

Regarding the Clustesaurus Rex I can build a separate VI for each manipulation which only uses the data it needs. But we want the MHL Action to be atomic, so there is only one single VI in that case which takes the whole Cluster in and out.

Would that be ok? Any other suggestions?

[Taggart]

In general, my answer to Clustersaurus Rex is object composition.  Does it make sense to break your big cluster into a series of related objects? 

Also if you are moving around lots of image data, it makes sense to be concerned about memory usage and data copies and consider using DVRs and IPEs.

[AlexElb]

Thanks for your suggestion. Data Value References and In place Execution look promising in matter of performance. I'll have a look at it later.

I guess for my learning experience in LV I should first get into object oriented design. I'll try to get back here with a DQMH Settings Editor Module which uses object composition for discussion and feedback.

Could you point me to some starting points when DQMH meets LVOOP?

And would it be okay to pass my ModuleObject into every SubVI as proposed in my first question?