LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Petru_Tarabuta

New gesture to create Unbundle By Name node (Ctrl + double-click when creating a cluster wire branch)

Status: Declined

QuickDrop works well for accelerating this workflow. Also, I want to reserve the key modifiers on the wire-and-double-click gesture for possible future additions of related editor operations.

Recently LabVIEW has added the following feature: When creating a new wire, double-clicking creates a terminal. This can be an indicator or a control, depending on what was selected. If the wire was started from a data sink (a structure tunnel or a subVI or node input terminal), holding down the Ctrl key while double-clicking creates a constant. This is very useful and saves time. Kudos!

 

When working with cluster wires, it would be useful if an Unbundle By Name node could be created by:

1. Start creating a new cluster wire or wire branch

2. Hold down a modifier key (Ctrl, Alt, Shift, or a combination thereof) and double-click

 

Step 1: Start creating a cluster wire

1 (edited).png

 

 

 

 

 

 

 

 

 

 

 

Step 2 - current behaviour: double-clicking creates a terminal. This is useful. Holding modifier keys down (Ctrl, Alt, Shift) does not alter the behaviour.

2 (edited).png

 

 

 

 

 

 

 

 

 

 

 

Step 2 - desired behaviour: Holding modifier key + double-click creates Unbundle By Name node

3 (edited).png

 

 

 

 

 

 

 

 

 

 

 

Notes

  • Creating UBN nodes is a common, repetitive action when working with clusters. This gesture would save time.
  • The screenshots above show a cluster wire being created starting from a control terminal. The gesture should, of course, work regardless of which object the wire branch was started from (e.g. tunnel, subVI output terminal, etc).
  • Perhaps the idea can be expanded to creating Bundle By Name nodes. Perhaps one modifier key (e.g. Ctrl) would create a UBN node, while another key (e.g. Alt) would create a BBN node.
12 Comments
Darren
Proven Zealot

> Does Quickdrop save the generated list somewhere?

 

Are you referring to the list of palette items? If so, then yes, it behaves as Wiebe described. But this is independent of Quick Drop... by default, LabVIEW will load palette contents in the background as you're using LabVIEW. So if you've been using LabVIEW for a few minutes after launch, and then you press Ctrl-Space, Quick Drop should be usable instantly, as the palettes have had a chance to completely load. But if you press Ctrl-Space immediately after a blank VI appears when launching LabVIEW, then you'll see the Populating List... Please Wait message in Quick Drop, as it needs to load the palettes completely before you can select something. Then subsequent launches of Quick Drop should be instantly usable.

 

But if you're referring to the list of project items, that behaves differently. The entire project is parsed for VIs, typedefs, and classes every time you press Ctrl-Space. Now, I could envision a situation where the first time this is done, there might be file access that needs to be performed on some/all project items, which may make the first Quick Drop launch slower, and then subsequent launches will be faster. But that is the case with any editor feature that requires touching files... at that point, we're relying on the OS's file caching to speed things up with subsequent uses.

JoGra
Member
@darren wrote:
If you press Ctrl-Space immediately after a blank VI appears when launching LabVIEW, then you'll see the Populating List... Please Wait message in Quick Drop, as it needs to load the palettes completely before you can select something.

Yes that's it.  I have been switching branches a lot, reopening the project every time, probably that's why i noticed the loading time.