ocmyface

Thanks for the input all! Shaun, I will check out your example. I've looked into the others as well. I think I am going to rethink my UI and make the operators deal with learning a new (and better) UI

Hello All, First time posting here, but by no means new to LV. I'm working on a DAQ application, and am curious how people would implement the following. The only ways I can really think of seem brute force, and I am sure there is a more elegant way. I am writing an application for some Agilent benchtop DAQs. Each channel of the DAQ can be configured as various types, and each type has a different set of parameters (ie temp has thermocouple type, strain has bridge config, etc). I want the user to only see the parameters applicable to the channel type they select for that channel. So I'm picturing a configuration cluster for each channel type, then when the user selects the channel type from an enum of options, next to that will be the configuration cluster. Change the channel type, and the cluster changes with it (Similar to how Agilent's Datalogger already works if anyone here is familiar.) Normally I would use an enum to drive a tab control and display the appropriate information. But that doesn't really work for this application as I am going to have upwards of 70 channels to be configured. That's too much to handle on a per-channel basis. I have not messed with LVOOP, but I feel that is probably the best way to do it. A parent "Channel" class with child classes for each channel type. When a user selects a different channel type, it becomes a different child class with different data. However, I don't want to put the time into learn LVOOP and then it end up not giving me what I want as I am on a very short timeline here. How would you do this? Any ideas? Thanks for your help!