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!
I feel I am the only one who thinks the Front Panel is archaic. I would like NI to develop new controls. e.g. left/right/up/down arrows to name 1. I would also like NI to provide a minimum of 5 different styles of controls, or allow us more flexibility to design our own. I'm so tired of the button and control selection looking so "yesterday". NI has done such a great job at updating the diagrams, but I feel the FP needs Much Attention! Please post your thoughts on this (agree or disagree).
I want to have the possibility to use a probe directly on an iteration terminal.
When using a loop (for- and while-) I sometimes would like to see how many iterations that have past since I started. This is easily obtained by using an indicator connected to the iteration terminal or using a probe on a wire from it, but if I forget to create an indicator and I don't use a wire from the terminal I think it would be great to just right-click on the iteration terminal and create a probe.
I suggest that radix is always visible when the numeric display format is other than decimal. Is this number decimal for instance?:
Well, it was hex:
... -> ...
Basically you'd know that if there isn't a radix visible, then the number is decimal. It should still be possible to show radix for decimal numbers as well. This should be the case for both constants and controls/indicators.
Just one of those little things that would enforce a minimum of documentation.
I'd really like to be able to select the entire top-level cluster in an event structure, if event data is a cluster:
I know this have been brought up in numerous forums over the years, but I feel it's being ignored somewhat by NI? It usually gathers quite a few positive acknowledgements from other users, but I think it's about three years since it's been brought up in the idea exchange. It seems so easy to implement and would greatly simplify many event structures. So forgive me for duplicating something from countless other places, but I think it deserves a second (or ninth or whatever) glance
I am a habitual right-clicker, it is an ergonomical method to perform many tasks , so long as the right-click menu isn't too long and is configured well. When I select multiple BD objects I would like to have more options than 'Properties' from the right-click menu. In particular I would
like to be able to Clean Up Selection and Remove
Broken Wires from Selection. Other possibilities include Align, Arrange, Group and Create SubVI from selection.
Disclaimer: One ulterior motive is to provide an alternative implementation for Remove Broken Wires (Ctrl+B) so that the keyboard shortcut can be freed for its much more natural use as Bold. Of course I am advocating a selective approach where it is limited to a selection. IMO the VI wide implementation is more trouble than it is worth, and certainly is not so useful that it should occupy prime keyboard shortcut real estate.
When selecting properties from the Y Scale, I would expect to get the properties window opened for that axis. But no, you get the properties for the x-axis. But I distinctly selected the properties from within the Y Scale. See image below.
My suggestion is to open the properties window to the axis where the selection was made from.
When doing UI work, it can be quite frustrating rewiring hidden controls to the connector pane. You have to go to the block diagram -> Show Control -> go to front panel and wire it up then hide your control again.
My suggestion is that when you select the Wiring Tool on the front panel or click on the connector pane (to wire up a terminal) all the hidden controls would become partially visible and become connectable to the connector pane.
At present case structures have options (right click) to create multiple cases if enums are attached to the case selector. If someone want's to reuse the same case structure with less number of items in a new enum, one has to manually delete one case at a time. Having an option to select multiple cases to delete, or automatically delete broken cases would be desirable to speed up things.
When entering values into an array control, you can <tab> between the elements while the VI is running. This same behavior should be available when editing elements in an array control (when the VI is not running) and an array constant.
You can open a type definition by right-clicking a diagram terminal, constan, or front panel control, but it is not possible to get to a type def file just from a wire. There are a lot of times where I'm working on a diagram that uses a type definition that is only exposed as a wire. Right now, the process of getting to the type def is to create a temporary constant from the wire, then right click the constant. It would be nice to make it easier to get to the type def. And of course, I would like to have the same functionality for LabVIEW classes.
When building an installer to let an application run on another computer one should select all the installers of products used in his porgram. This can be really tricky, especially to new users, that don't know if a VI was included in package A or B or if it's already included in the standrad runtime.
Therefore it should be possible to hit a button, that parses through the Application and determines which packages are used.
I though of writing something like this myself, but I can't be bothered
You'd just have to parse the Project, check all the VI names and relate it to a table that contains information, about where a VI comes from.