LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
sriveni

Grouping the Controls in the Event Sources by Tab Control Pages in the Event Structure

Status: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.

Hi

This an extension to the idea which I have submitted.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Displaying-Tab-Page-Names-in-the-Block-Diagram-when-ac...

I had difficulty when accessing the control names on the front panel have more number of controls and also when we have same control names in the different pages of Tab Control.

It would be good if they can be grouped by Tab Page under the Event Sources in the Event Structure as shown below. This is similar to what the LabVIEW does when displaying the Cluster Variables in the Event Sources.

 

Tab Control Events.png

 

It will be helpful it the idea can be extended where ever accessing the controls/Indicators from the Tab Control Pages.

 

Thanks

5 Comments
Intaris
Proven Zealot

Please keep things in one place.  You are free to extend ont he original idea as a comment of the original idea instead of creating duplicates.

AristosQueue (NI)
NI Employee (retired)

In this case, Intaris, I'd rather these be separated. The ideas are related but not identical. I am not sure whether if we did one that we would necessarily do the other.

Intaris
Proven Zealot

I still maintain having multiple controls with the same name is behaviour which should be discouraged (It's also given here as part of the motivation).

 

Having said that, if I had to choose one of the two ideas, it's be this one (because it has benefits beyone controls of the same name).

AristosQueue (NI)
NI Employee (retired)

> I still maintain having multiple controls with the same name is behaviour which should be discouraged

 

Oh, definitely! Personally, I'd make that change to LV, but I understand why it doesn't happen. Every couple years we have a debate within the R&D team about breaking VIs that have multiple controls with the same label. It's always clarity of programming vs ease of UI writing. I've not heard any ideas for improving the status quo that would allow us to force unique labels without burdening a lot of users in sriveni's situation. Somehow you need to be able to say "look, the user gave both of these the same name, but that's really just the caption, so we'll display the caption but use the label on the diagram, but how does the user know which label we automatically changed (say by adding a "2")? And do we change it back when the user removes the offending duplicate? Do we always display captions? If so, how do we know when to keep the labels up to date and when not?"  There are lots of easy answers to these questions for 80% of use cases, but they get bogged down in details, and those details are usually the cases that are driving the desire for unique labels in the first place!

 

"Force labels to be unique without creating an editing burden for people who need multiple controls on panel to have the same caption" -- if someone had a really fleshed-out idea for how to do it, I'd love to see it on the Idea Exchange. Just saying "NI should do this" won't help. 🙂

Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.