NI Home > Community > NI Discussion Forums

LabWindows/CVI Idea Exchange

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea

polar plots

Status: Under Consideration
by Trusted Enthusiast on ‎10-28-2010 05:34 AM

It has been discussed a few times in the forum so it might be appropriate to also ask here for the implementation of a native polar plot, i.e. plot r versus theta, with radial grid lines and all the corresponding ingredients.


Button with picture and text

Status: Duplicate
by Member ZVS on ‎10-27-2011 07:49 AM

Command / toggle button with text and picture like this: Button with text and Picture (sorry for Russian text :smileywink:)

Status: Duplicate

It has been suggested earlier (here) to provide the LabVIEW feature of a display format 'SI notation' allowing to directly enter 100 kHz (instead of 100000 or 1e5)


status bar control

Status: Under Consideration
by Trusted Enthusiast on ‎02-18-2011 07:14 AM

Over the years the look of CVI's control elements got closer to native Windows controls, e.g. by the direct use of native Windows controls such as the File Select Popup, which I would consider a welcome visual improvement.


What still is not available is a control element providing a Windows-like status bar, e.g. like the one of CVI's IDE.


I imagine a status bar which is similar to use as a menu bar, i.e. with a LoadStatusBar command, similar editing capabilities and the possibility to define the number and type of elements (text, image,...). Also the lower right part should resemble the typical Windows 'triangle', see figure below.






Specify the configuration to include into installer

Status: New
by Active Participant vix on ‎12-12-2011 01:14 AM

Using CVI 2010 you can create different Custom Configurations

But I think that if a developer creates a new Custom Configuration (debug or release, x86 or x64), he wants to distribute it to a target machine. I don't create a Custom Configuration to have it run on my developer machine!

I've already asked to NI Support, and this can't be done in an automatic way.


So I suggest a new feature in the "Edit Installer" window to specify which Configuration (Default or Custom) to include into the installer (see attachments)

Status: New



following the discussion here I suggest to (more clearly) indicate the number of allocated rows and columns in the UI table editor.


I imagine something like



where the left number indicates (as now) the currently selected row, and the right number (11 in my quick example) indicates the number of all table rows.


The same might also be added for the number of total columns.



Status: Completed

vertical button text

Status: New
by Trusted Enthusiast on ‎03-17-2011 11:40 AM



sometimes vertical buttons or toggle buttons fit better to the rest of the UI than the standard horizontal buttons. In such cases I would like to have the possibility to have the button text aligned vertically. Hopefully the attached figure can explain my wish...




Goto Declaration

Status: New
by Trusted Enthusiast on ‎11-11-2011 09:36 AM

In the process of developing a function one typically has to change the number (and type) of parameters. This has to be done both for the function and the function declaration. Hence I would consider it useful to have an option 'Goto Declaration'.


Right now the IDE provides the right click menu 'Goto Definition', so if I change the declaration it is easy to jump to the function and adjust it accordingly. It would be nice if the reverse process would also be possible...




Sizeable dialog for batchbuilt

Status: Completed
by Member Peter_Prinzen on ‎04-07-2011 02:53 AM

I want the batchbuilt window sizeable.


My cws consits of 51 projects, and the configurations-list is no longer useable. I just can see the project names, but not able to see the "release/debug/..." additional informations of the projects to be built. The list looks like

" c:/../../Task_AutomaticMeasurement.prj - D"

" c:/../../Task_FullAutomaticMeasurement ..."

Status: Completed

Allow for smaller distribution kit sizes

Status: New
by Trusted Enthusiast on ‎09-17-2013 02:37 AM

As discussed here, distributing the code of


#include <ansi_c.h>
int main ( int argc, char *argv [] )

    printf ( "%s", "Hello world" );


generated in CVI2013 results in a distribution kit of 74 MB minimum...  Using the NI default settings results in 219 MB...


Yes, I do have TB drives, but I dislike bloated software.


Creation of subfolders in the project window

Status: Completed
by Active Participant vix on ‎10-13-2010 01:49 AM

In the project window you can organize the project files into some "virtual" folders (Source Files, Include Files, ...)

If you right-click on the project name, you can add a folder with the item "Add Folder...".

If you right-click on one of these folders, you can add one or more files files.


But it's impossible to create a subfolder of one of these folders.


Every large project has a lot of files (sources, ini-files, images, icons, ...), so I think it's quite common having them saved into different "real" folders and subfolders. If you don't explicitly add these files to the project, you can add them to the distribution kit browsing your hard disk "real" folders, but in this situation the absolute path of the files is used. And if you move all your project from a PC to another one you won't be able to recreate the distribution kit without errors if you don't save the whole project to the same folder you use in the first PC.

And this is a really big problem.

For files explicitly added to the project, instead, the relative path is used, and this is OK, so the best situation is to add all the files in the project window.

So it's necessary create a full structure of virtual folders and subfolders.

Status: Completed
Introduced in LabWindows/CVI 2013

Tree Control: Copy Selected Rows to Clipboard

Status: Under Consideration
by Member kevin.key ‎04-28-2011 07:27 AM - edited ‎04-28-2011 07:30 AM

It would be nice if you could copy the selected rows of a tree control to the clipboard.


tree example.png


Graph improvements

Status: Completed
by Member Bertrand_ENAC on ‎02-05-2011 02:20 AM



I have 2 suggestions for graph improvements.


1/ I suggested the first one a long time ago but it has never been implemeted so I try again trough this idea exchange board.

I would like to have the possibility to change the grid lines style to dash or dot. Today only solid is available.

I have written a routine to do it for printing graphs but as you can see it in the attachment it is not always working properly.


2/ It would be nice to have the possibility to set a percentage of transparency for the plots. In the example attached you can see if the green plot would have been behind the blue some parts would not have been visible. By setting the percentage of transparency of the blue one the green if behind the blue would become partly visible.


These 2 features are already available in the 3D graph so it would be nice to have them also on 2D plots.




Status: Completed
Introduced in LabWindows/CVI 2013

As discussed here and here, CVI does not re-open workspace files in the order they were when CVI was closed; I am referring to confined workspace, not freely floating windows.


As a result, starting CVI one first has to locate all the files, where did the include file go...? If you happen to have some more tabs this is a waste of time.


Also, as Roberto mentioned, you can not easily use the short cut keys Ctrl-1 etc. because of the changing assignment.


So, in short, I am asking to improve this behavior and maintain the tab order of CVI workspace files, that is, re-arrange/re-open the tabs in the order they were when CVI was closed.





it has been discussed a few times in the forum of how to implement a check box control in a table, e.g. here. At present, this type is not natively supported. In principle, as second best possibility, one could use suitable image controls, but the 'correct' image of a check box depends on Windows version, theme, etc. Hence it would be much nicer to have a native check box control - thanks


Brave New World of WPF Graphics

Status: New
by Trusted Enthusiast on ‎08-08-2012 02:28 AM



There are several quests for better graph and UI controls, and I support them all :smileywink:


Now, I was very impressed looking at the new WPF Graphic controls of Measurement Studio 2012 and would like to have similar features in C (i.e.CVI), too.


So in addition of having classic controls and lab style controls may by one could also add this new scheme of controls...??? The graph control in particular looks very promising, with color gradients and polar plots, both frequently requested features, here realized in a new style. Wanna have...


For a fist impression, see here 




Data Tooltip Should Display Function Name Of Pointer To Function Variable

Status: Under Consideration
by Member Johannes_T ‎09-05-2013 09:08 AM - edited ‎09-05-2013 09:09 AM


Data Tooltip should also display the name of the function, when displaying the value of a function pointer variable.



While debugging a CVI application, when hovering the mouse cursor over a function pointer variable, the Data Tooltip displays the address of that function, referenced by the variable.

It would be very useful in cases when you have multiple function pointer variables referencing several different variables, to have the Data Tooltip not only display the address of those functions, but the name of the functions as well.


Data Tooltip With Function Pointer


From the CVI Help:


Some Interface to Win32 Application Programmatic Interface (API) functions have the same name as some LabWindows/CVI functions, causing a naming conflict. You must include the Interface to Win32 API include files before the LabWindows/CVI include files. LabWindows/CVI automatically resolves the conflict by using the LabWindows/CVI implementation of the function. To use the Win32 API implementation of the function instead, define the SDK_CONFLICT_PRIORITY macro in the Compiler Defines section of the Build Options dialog box.

If you enable the SDK_CONFLICT_PRIORITY macro, you cannot use the following LabWindows/CVI functions and should use the Win32 API implementation instead.

Formatting and I/O Library

  • CloseFile
  • OpenFile
  • ReadFile
  • SetCommitMode
  • WriteFile

Utility Library

  • Beep
  • CopyFile
  • DeleteFile
  • GetFileSize
  • GetFileTime
  • GetSystemTime
  • SetFileTime
  • SetSystemTime
  • inp
  • inpd
  • inpw
  • outp
  • outpd
  • outpw


Based on my experience these name conflicts have no advantages, and create a lot of problems: usually I use the CVI implementation, but it happens that after some time I need the Win32 API implementation of one of these functions (GetSystemTime(), for example).

In this situation I must heavily modify my code, changing the calls to all the above functions.


I don't like these naming conflicts at all.

I suggest that a "_CVI" prefix (or something like that) is added to the CVI implementation: an old project will recompile perfectly simply adding this prefix to the calls, without modifications to variables, structures, ...

We're currently in the era of the large widescreen monitor.  Can we have the title bar in the IDE show the full path name of opened instead of abbreviating it with '...' if the window is large enough to show the full path name?  Thanks.

Status: Completed

I made this suggestion some time ago - unfortunately I had combined it with another, related idea. The other idea was implemented so now the complete issue is dead, sorry, completed. :smileysurprised:


This suggestion is meant to revive the unfulfilled request of two new attributes, allowing to dim and hide a specified entry in a ring control. This would be convenient as it avoids to programmatically rebuild the control.





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