Leaderboard

I use methods and properties on the diagram all the time. However, I also use clusters or arrays of ctrl references passed into subVIs as well. I don't think it's a good idea to manipulate UI objects from within a class unless the main purpose of that class is to manipulate the UI. Like a UI class. In your example, I would create a method called Engine State. I would read that state, and if the engine was running, I would disable the button.

Hi durnek60 I use a combination of both along with handling it directly on the BD depending on my requirements. The only issue I can point out with Classes is that you cannot have a XControl reference as private data - well technically you can, but your build will break . In those cases I therefore use a Class and a MFVI for the X-Control or just use a MFVI for everything. Of course for small dialogs etc... where I feel I do not benefit greatly from encapsulation etc... then I do stuff straight on the BD cause its easier. Cheers -JG

I forgot to check LV 2010 before the SP1 patch. Well, I'm sorry it broke, but I'm glad we fixed it.