LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW 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 Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Authors
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

block diagram decoration frame element with clustering ability

Using single-frame-sequences is one (beside other) possibility to keep the code well structured and good readable:
- clustering code in logical groups
- defined place of description by using sub-diagram label
- frame- and background colors
- exclude from diagram cleanup option
- moving the frame will move the code inside, too


But there is also two disadvantages:
- clustering the code in sequences changes the execution order. Especially on high optimized and parallel code this can lead to unwanted performance loss
- only code which follows the data flow can be placed within one frame


An alternative is the frame decoration element. But this is not grouping the code, it is just floating over the code. This has several disadvantages:
- during diagram cleanup the frame will be moved to somewhere
- moving the frame will not move the code
- documentation ability
- no background color

My idea / request:

The frame-decoration-element shall be extended by a visual code-clustering ability so that it has the same usability like a sequence but without an influence to the execution order. Additinally it shall be possible to place code inside, even if this does not follow the data flow.


The two images are showing the current situation - first with a decoration frame, second with a sequence.



Remark: I'm using LV2015SP1     


Proven Zealot


This idea has been repeatedly rejected by R&D.

It originally came up when we were designing the Diagram Disable Structure. If you're disabling two sections of code, there's no reason to necessarily slave their dataflow together. So we originally prototyped it as exactly what you're requesting -- a structure that could group code without modifying the dataflow. But in usability testing, we found that confused more people than it helped. Ultimately, we decided that frames in LabVIEW need to always be synchronization boundaries. We have revisited this question a few times over the years and always come to the same conclusion.


hm ... ok Smiley Frustrated  😞

Proven Zealot