Cascaded Case-View

[muks]

A multiple case structure is always difficult to navigate to and understand. A toggle option like the below will add clarity

Please note the Case summary text option suggested in the right of each case in this view. In the present view you have to navigate to each case to get a glimpse of what is done. A simple summary like below will add a lot of clarity and help in understanding what is actually being wired in the subsequent cases (just an example)

Will be helpful while dealing with multiple case structures isnt it?

[johnsold]

Use of an enum rather than a numeric for the selector would give you the self-documenting feature.  That has long been a part of LV.  I can't see enough advantage over clicking the down arrow and looking at the list to justify the loss of panel space.

Lynn 

[muks]

I accept using enum will give the description part. My suggestion is to keep this as an optional toggle.

Even while using enum you need to navigate and see the summary of other cases. You cannot make sure eveytime you can use enum. The down arrow is for documentation only and not the list of other cases.

[muks]

For example If you click on "Communication with plc". It can have a text box explaining the communication protocol and the order of communication. And my suggestion is to again make this optional for the users to choose.

[smercurio_fc]

I honestly can't quite figure out this idea. I also agree about the the loss of panel space. What happens when you have 20 cases? What happens when you add cases? Does the inside "shrink" to account for the additional case, or does the outside boundary of the case structure grow? If it shrinks, then you have less to look at. And if it grows, what happens to the rest of the code around it?

[Intaris]

Wouldn't just giving each FRAME of the Case structure its own label be a much better way of solving this problem?  I say problem.....

[muks]

intaris wrote:

 Wouldn't just giving each FRAME of the Case structure its own label be a much better way of solving this problem?  I say problem.....

  A TOGGLE view is what is being suggested. I am not tweaking with the original existing view in anyway. A key board shortcut can show me this view for clarity......

[Intaris]

But how is this different from using an Enum for a selector or using the case preview function?

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.