Tip Strip on Case selector must display all the values if the case has multiple values

[P@Anand]

When we have multiple Enum values using a same case it is difficult to see what are the values using it. It would be good if we have a Tip strip showing the values handled in that particular case would be more meaningful instead of having "Selector Value" as a tip strip.

There is also an idea on removing the tip strip totally and it got fair response.

Please ignore if already suggested!

[P@Anand]

This image is totaly irrelevant  Exaggerated from the Idea which I proposed so don't get carried away as the original idea deals with the Non-Consecutive numbers/Enums.

[X.]

It's called exaggeration.

[P@Anand]

It's called exaggeration.

Yeah, thats the right word 🙂

Edit: I got time to edit my comment

[AristosQueue (NI)]

I'm speaking here as a LV User, not as a member of LV R&D.

For me,

       "TwoHundred".."FourHundred"

already lists all the values in a nice compact form. Listing all the values in this case is usless noise, in my opinion.

What would you display in this case?

If you try to display all the string values, that's going to get a bit ridiculous.

I would find an expanded tip strip to be useful when the case is clipped by the width of the case structure, like this:

[P@Anand]

I am repeating again ( I should have edited my original Idea description). The Tip Strip would display the non-Sequential values. I wouldn't mind displaying 1..9999. But in a case if I have skipped values inbetween and if the case selector becomes narrow I am missing the values and I have no way to know unless scrolling into the case selector value. 

As you said the main idea behind is the values getting clipped for non-sequential values

[AristosQueue (NI)]

Ok. We're on the same page then.

[X.]

Just reminding folks that the "range" feature of the case structure is a double-edged sword:

prevent automatic change from selector value list to value range

LV feature? Editing a list of cases with ellipsis...

[AristosQueue (NI)]

> the "range" feature of the case structure is a double-edged sword:

Yes. That's a separate issue, but I agree.