LabVIEW
Resize Radio Buttons?
Solved!
@JÞB wrote:
Except that we associated related controls by logical groups and then smushed all the code for those separate groups on 1 block diagram. I Hate Tabs. They are the Stacked Sequence Structures of the Front panel.
Not necessarily. I make heavy use of front panel clusters and arrays (often with transparent containers, so you would even notice ;)), so things are logically grouped already. In simpler programs, the tab value is not even connected anywhere in the code or triggers any events. it's use is purely cosmetic. We don't need to know the tab value, because if a control fires an event, it is obvious that that control must be on the current tab. A lot of things (on many tabs!) need to be recalculated and updated, no matter what tab that control is located.)
It really depends what the program does, but my program often need so many controls and indicators (example) that it either will not fit on a smaller resolution screen, would require scrollbars, or would require significantly more code if we do it without tab controls. I understand that in other application areas, tabs are often not needed. But we cannot generalize that to everything.
Hey look, my chrome browser even has tabs! If it is good enough for Google, it's good enough for me! 😄
So, everyone argues from a specific narrow perspective and comes to different conclusions. Seems obvious. 🙂
Just saying that subpanels would require significantly more code and more subvis in my case. Each tab has groups of controls with visibility determined by the state of other controls, often located on different tabs. I would need to carry control references around everywhere. All I currently need is a tiny parallel loop with its own event structure, which listens out of band for value changes, updating properties of other controls accordingly.
During use of my programs, tabs are flipped often. I would like to see a performance comparison between flipping a tab (no code needed) and inserting a subvi into a subpanels (lotsa code needed).
Tabs are nice, fast and direct. Code only gets clunky if the beginner programmer connects it to a case structure, trying to micromanage what code parts run as a function of tab state. Herding cats is easy by comparison :).
@JÞB wrote:
More sub is yes.
So how do you suggest to modify any control/indicator properties (disabled, visible, etc) on any of the other subVIs (loaded or not into a subpanel) based on control value changes on the panel of subVI currently loaded into the panel. The combinatorial explosion of possibilities is mindboggling. 😄
