LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

Collaspe and expand in switch structure

Under labwindows CVI 2015, I develop a program using a state machine. For this I use a "switch".
The program is voluminous, and in order to browse it more quickly, it would be very interesting to allow the collapse and the expansion of the boxes in a structure "switch"

Knight of NI

This problem sounds analogous to someone trying to code an entire LabVIEW program in one VI taking up numerous screens.  If you have long stretches of commands within a switch structure, shouldn't each of those sections of code be made into a subroutine?


Of course, and it's already done. But that is not enough
The collapse and expansion is operational for all other strcutures (if, for, while, do ...), so why not for the "switch"

Trusted Enthusiast

Of course, for reasons of consistency, switch statements also should be collapsible.

However, they already are (at least in CVI2015 SP1)


I only have the version CVI2015 base.
I'll see to install the SP1.
thanks for the information.

Proven Zealot

The typical state machine built into a switch has normally very large code in each switch case. In this case it would be practical to collapse single cases code, while at present only the while switch can be collapsed. I suppose this is what AfgVD is looking for, and surely is what I would look for!

Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
If I have helped you, why not giving me a kudos?

Hi AfgVD,


Thanks for your post! I think I understand what you're looking for but just to be sure, in addition to being able to collapse the switch statement itself, you want to be able to close all of the cases themselves, is this correct? 

So from this:


To this:case_close.png

Collin D.
Software Product Manager
Status changed to: Under Consideration
Collin D.
Software Product Manager



Yes it is exactly that