Organizing 2000 Controls

[jshatzma]

I'm writing a VI that has nearly 2000 controls (switches and slidres).  There are about 16 elements that each have the same ~120 controls.  I want to use a tabbed interface to switch between the 16 elements to save space on the front panel but doing this causes huge headaches in the block diagram because it makes a massive number of screens full of the controls.  Any thoughts on how to organize such a massive interface?  I thought about using a case structure to sort of make tabs in the block diagram but I can't use the tabs from the front panel to create any sort of numeric control, and I'd like a clean interface (i.e. don't want to have to have tabs to show the correct controls and another selector to tell the block diagram to update the corresponding controls).

Thanks,

Jeff

Message Edited by jshatzma on 08-17-2007 11:05 AM

[jshatzma]

Nevermind, I'm a fool.  It does give a numeric output...the defeault 'make indicator' is another tab for whatever reason.

[Ben]

HI Jeff,

Could you post a screen shot of what you are attempting?

We may be able to advise on how to do this with far fewer controls.

Just trying to help,

Ben

[Dennis_Knutson]

Instead of trying to determine how to organize so many controls, I would use the same 120 controls in the 16 different situations. Then I would try to reduce the 120 controls to something reasonable. I agree that we need to see the code or at least an image to determine why you need so many.

[falkpl]

Logical grouping is required.  First make a cluster of each set of 120 controls, i would furthur break this cluster into several supgroups.  Use typedefs.  Your block Diagram will have only 16 controls now,  Each control can be unbundled into several subgroups and the subgroups can be logically grouped by functionality.  This will allow you to scale your application and manage it.  2000 controls in not a good ides.

Paul

[Ben]

Paul wrote " 2000 controls in not a good ides."

Well at the very least it is scary.

Ben