LabVIEW APIs Documents

Showing results for 
Search instead for 
Did you mean: 

Quick Drop Keyboard Shortcut - VI Server Rename

NOTE:  This shortcut ships with LabVIEW 2010 and later.  You should only install it from this page if you are running LabVIEW 2009.


The attached Quick Drop Keyboard Shortcut will allow you to rename the class of a Class Specifier Constant, Property Node, or Invoke Node, without having to navigate the class hierarchy right-click menu.  It also allows you to specify the property or method of a property or invoke node, respectively, without having to navigate the property/method right-click menu.


Class Rename

1.  Select one or more Class Specifier Constants, Property Nodes, or Invoke Nodes on the diagram.

2.  Press Ctrl-Space.

3.  Type the name (case-insensitive) of the VI Server class you wish to specify (i.e. "vi", "control", "forloop", "multicolumnlistbox", etc.)

4.  Press Ctrl-B.  The class of the selected object(s) will be changed to whatever class name you typed.


Property/Method Rename

1.  Select one or more property nodes on the diagram.  Alternatively, select one or more invoke nodes.

2.  Press Ctrl-Space.

3.  Type the name (case-insensitive) of the property or method you wish to specify (i.e. "visible", "disabled", "connect wire", etc.)

4.  Press Ctrl-Shift-B.  The property or invoke node(s) will be changed to whatever property or method you typed.


Installation Instructions

Save in your [LabVIEW 2009]\resource\dialog\QuickDrop\plugins folder.  No LabVIEW restart is required.

Active Participant
Active Participant

Very cool!

I did notice a bit of inconsistent behavior.  For instance, I couldn't change an application invoke node to 'Get VI Version.'  The property node also appears to require more precision when typing the name.  "buildnumber" and " number" changes the application property node to OS.BuildNumber while "build number" does not.

Proven Zealot
Proven Zealot

Thanks for the feedback, Daklu.  Unfortunately, the name you see on a property/invoke node doesn't always match the internal name of the property/method that is currently exposed in scripting (I am going to file some CARs on this shortly).  You'll notice, if you look at the diagram of, that I try all sorts of iterations on what is typed to see if I can find a match.  I added a few more iterations that play with the spaces in what was typed to try to find the match, and these fixed both the OS.BuildNumber property and Get VI Version method you mentioned.  You can download the latest version of to check out the updates.