Case strucutre ctrl+scroll should display cases

[1984]

Using ctrl + scroll for switching between the cases is somewhat hard to use, because when you have lots of cases its difficult to remember what is the order of them so its harder to ctrl scroll the one you looking for than to go to the case selector. Moreover if you work with bigger sized structures (which happens sometimes) you may not even have the case selector on your screen so if you ctrl scroll, you can only deduct which case you see by the visible part of the code itself. That doesnt work for me, I always go to the selector.

But what if when the user uses ctrl + scroll a small popup would appear at the mouse pointer and when the user scrolls up and down the highligh would move up and down selecting any case in the given structure?

This would highly increase the usability.

Applicable to the Event structure as well.

[tst]

I agree that for many cases this could be useful, but it will probably be annoying with few cases and you're trying to toggle back and forth quickly. If it was implemented, it should probably have a delay built in where it only appears after you hold down Ctrl for a second or two.

[dthor]

Instead of CTRL+Scroll for the reason that tst mentioned, how about CTRL+Right Click inside the structure?

After the list of cases comes up, you could just click on the case you want *or* use the scroll wheel to cycle through them as mentioned in the original idea.

This way the original CTRL+Scroll behavior is not changed.

[AristosQueue (NI)]

What if we just opened the existing selection ring while you're doing that and moved the selection line through the ring? For short case structures, it would always be up at the top and you'd just be moving back and forth between true/false or whatever your cases are.

[tst]

AQ, that seems reasonable. Since you don't necessarily know where the cursor is exactly when doing this, this will also give a consistent place to look for the list.

[1984]

Opening the default selection ring makes sense in some cases but it does not address the problem when the selection ring is not on the screen.

[ThiCop]

Trying to follow the reasoning:

Due to what reason is your selection ring not on the sceen?

Is it due to the size of the case structure in the block diagram that exceeds the current sceen size?

[1984]

Correct.

[AristosQueue (NI)]

> Is it due to the size of the case structure in the block diagram that exceeds the current sceen size?

> Correct.

AH. The solution is obvious! Ctrl+scroll on such a giant case structure should auto create a subVI for every frame and then reduce the size of the case structure and THEN show the selection ring!

🙂

[1984]

That would be a long shot, I guess.

[AristosQueue (NI)]

Regardless of implementation, the basic theme behind this idea is reasonable -- some way to show what you're scrolling through. The particulars of implementation would be investigated by R&D if we choose to undertake the idea.