Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Do you have an idea for LabVIEW NXG?
Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!
From early on in labview i've had issues with larger VI's not being completely visible on the screen, making it more difficult to 'wire up'. Other suggestions have been for resizing the front panel, but resising the diagram would also be a very helpful feature.
Similar to the "view / zoom" window in IE8 or word to view more or less information on your screen at once. Hopefully this would come with a hotkey option as well to quickly increase and decrease the zoom level during code writing.
It would be great to have a feature similar to the Microsoft 'Format Painter'.
Sometimes in a project you need to change an amount of indicators from one data type to another (U8 to U16 for example) or, you want to change the number of digits of precision, string indicators from Normal to Hex etc, etc.
A Format Painter would be great, highlight the format tool, click on the master object and then click all of the controls/indicators that have to be the same. The painter could work on front panel objects or block diagram terminals.
In many of my programs, it is frequent that I have to issue a command, then wait for a period of time before reading a response. Usually, if there is a timing delay in code, it is usual to end up with something like this:
To do this more neatly, I created a timing subVI with errors wired in and out, and a number wired to it, to instruct the program to stay in that subVI for that period of time. It takes up much less space.
By doing this, I can easily control timing and execution. However, it's be nice to rework the 'milliseconds to wait' diagram so we could wire errors through it, as this would make the block diagrams so much neater...
If i am creating a new control of the same type as the first one, for the second time, the name automatically changes by concatinating "space 1 ". that is fine. but simultaneously i have option of having the same name as the first control by editing. When i am creating variable it is confusing for which control i must relate it to untill unless i find the control and check.
I want to know (some kind of information on availability of the same name for another control) while editing the variable name of the same type is available.
If you have multiple version of LabVIEW opened, it is difficult to tell which version is which by looking an the windows task bar. There should be some differentiation between versions for easy identification.
arLos imagines de formato tiff permite guardar varios imagines en LabVIEW no tenemos posibilidad de guardar varios imagines en el mismo fichero tif ni leer los siguientes solo lee el primer imagen que encuentra en fichero,
quiero posibilidad de guardar y leer varios imagines en el mismo fichero tiff o cualquier formato estandar que permite varios imagines en el mismo fichero por ejemplo DCX,
Many developers have to program on laptops that usually come with a limited screen. How if in Labview, we could use a zoom capability on block diagram. It could works fine also using the mouse scroll. Very usefull to little screens .
I don't know if this idea belongs in the "LabVIEW" Ideas Exchange necessarily, but this idea is something that would really make a big difference to my LabVIEW development, so I offer it anyway: "Parallelise the FPGA Compiler to take advantage of modern multi-core computing power".
The FPGA compiler takes approximately four hours to compile my large FPGA VIs, which makes for long and tiresome debugging processes. It's clear that the compiler uses only one core of my CPU when compiling. If the compiler could be written to take advantage of the many cores of today's multi-core computers, it could potentially reduce my compilation times to an eighth! (Where I work we have an eight-core number crunching server ideal for just this task, and I'm sure we'll get even greater core counts in the near future - thinking GPU here).
I know the compiler is probably the intellectual property and responsibility of Xilinx Corp, and not National Instruments, but I expect NI can give them a big push if we all asked nicely for it!
When you make a build, Project Explorer concludes with a status box that tells you where the build "lives". This box needs to have a button "open folder", or at least make the status text selectable to ease navigation to the Build folder.
On occasion one needs to open the source code for a closed VI. The Project explorer window appears to be a good access point for browing and opening VIs. However, clicking on the VIs opens the front panel only. It would be great to have the ability to open the block diagram if one holds the <CTL> key while clicking a VI on the project explorer window.
All the time I make type def enum's in order to use with a state machine. Most of the time I create the enum from the block diagram instead of the fp. Maybe I should change my habit but I wish there was a "create type def" option on the bd right click menu so I didnt have to change to control, switch to fp, customize, then change back to constant.
In their current form, Auto-Indexing tunnels only operate on a single dimension of an array. For example. If you input a 2D array, through an auto indexing tunnel into a for loop, and display the resulting 1D array in an indicator inside the for loop as below, you will always get the last row.
I'd like to see a feature where you can right-click on the tunnel or something, and set it to auto-index by column, instead of by row, and get the last column instead.
It could be as simple as an option in the context menu for the auto-indexing tunnel to say "Index by rows" or "Index by columns" It gets more complex with 3D 4D and moreD arrays, but you could do something like a submenu flyout that says "Index By Dimension" > "1", "2", "3" etc