LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

grouping issue

Solved!
Go to solution

Hello,

                I am trying to accomplish something like shown in the picture. I know that I cannot group indicators and controls into single cluster. But can someone give me a workaround so that I can accomplish this.

Even in my UI they need to placed as a group and even in the block diagram it would be better if it acts like a cluster..because if i put the controls as individual control or indicator i would end up with

(5 button controls+ 6 Led indicators+ 1 combo box control) * 96 = 1152 icons in my block diagram. How do i overcome this?

Snap.jpg

“Talk is cheap. Show me the code.”
― Linus Torvalds
0 Kudos
Message 1 of 10
(5,730 Views)

Couldn't you make all of them controls (disable if necessary) and use a cluster control?

0 Kudos
Message 2 of 10
(5,727 Views)

Will it work? I mean, can I make the LED's as control and disable it so that the user doesn't click on it and change the color of LED in the disabled state?

“Talk is cheap. Show me the code.”
― Linus Torvalds
0 Kudos
Message 3 of 10
(5,725 Views)
Solution
Accepted by topic author arupoon8

Sure you can!

 

ArrayOfClusterControls.png

 

Message 4 of 10
(5,720 Views)

Yes. You can disable some of the controls in the cluster. In this case you want to Disable but NOT Disable and Grayed Out.

 

Note that you can change the state of the disabled controls in the edit mode.

 

To write to the controls being used as indicators, use a local variable.  This is one of the few legitimate uses for locals.

 

Can your user really make sense of 96 copies of that cluster on a panel? That seems like a lot of visual clutter to me. Maybe some way to select the active cluster or a small group for display.  If you take that appoach, then you could group separate indicators and controls. You would not need the disable and local variable. I would probably keep the data in an array or arrays on the block diagram.

 

Lynn

Message 5 of 10
(5,687 Views)

I've got to agree with Lynn's assessment.  Its very hard for a user to observe that much data at any one time.  You really need to pick and choose what details to display when you get to very large numbers of "Widgets."

 

Just to give you a taste of what I mean I'll show a screenshot of how I overcame "User Data Saturation" for a project the was used to monitor a large bank of sensors inside a F-24 Lightning II. (Used to test for EMI Hardness) and yes it was a fun little projectSmiley Wink

!0.png

The display on the left provided summary information for all sensors and permitted the user to expand to look at details on a specific sensor (the screen on the right actually loaded into that sub-panel on the main.vi

Color indicated general status (black being out of system) and the caption floating over the clusters provided current Temp, RSSI, Voltage or current at the user's discresion.  Clicking the cell selected which sensor to put in the detail display.  And of course everything got logged to a file.

 

Block Diagram management was a beast thoughSmiley Sad  things scale up pretty fast!

Spoiler
!1.pngThats just a portion of the main BD!  the rest is cleaner!

"Should be" isn't "Is" -Jay
Message 6 of 10
(5,676 Views)

@Jeff- Thanks for the response. I got really good implementation ideas from your answer.

@Johnsold- Thank you. Even though I group the controls and indicators I will still end up with lot of icons in my Block diagram. I am trying to see different ways i can group my controls

@Pianne- Thank you for quick response. Will try to check whether it will work out for my requirement.

“Talk is cheap. Show me the code.”
― Linus Torvalds
0 Kudos
Message 7 of 10
(5,654 Views)

@arupoon8 wrote:

@Jeff- Thanks for the response. I got really good implementation ideas from your answer.

@johnsold- Thank you. Even though I group the controls and indicators I will still end up with lot of icons in my Block diagram. I am trying to see different ways i can group my controls

@Pianne- Thank you for quick response. Will try to check whether it will work out for my requirement.


At least you can create the control refs with one fell swoop.  Jack's great idea hadn't been delivered when I developed that solution.


"Should be" isn't "Is" -Jay
0 Kudos
Message 8 of 10
(5,633 Views)

@JÞB wrote:

 

Block Diagram management was a beast thoughSmiley Sad  things scale up pretty fast!

!1.png

 In this case, you could consider the Controls[] property of a panel, Auto-index the refs in a For Loop, pull the "Label.Text" property off the Ctl Ref, and then group/sort with a regex. A wee bit more scaleable and more debuggable!

Message 9 of 10
(5,627 Views)

@JackDunaway wrote:

@JÞB wrote:

 

Block Diagram management was a beast thoughSmiley Sad  things scale up pretty fast!


 In this case, you could consider the Controls[] property of a panel, Auto-index the refs in a For Loop, pull the "Label.Text" property off the Ctl Ref, and then group/sort with a regex. A wee bit more scaleable and more debuggable!


D'OH!

IT NEVER OCCURED TO ME!  Do you know HOW LONG that chunk of code took me or how many mouse clicks?

 

bash-smiley-face.gif

Of course "debugging" wasn't an issue.Smiley Very Happy

 

 

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 10
(5,618 Views)