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!
It would be useful if a special free label existed on the block diagram and/or front panel whose contents would be kept in sync with the contents of the VI description. For brevity, let's call this a Description-Linked or DL label. The screenshots below show an example.
1. The DL label shown on the block diagram
2. The DL label shown on the front panel.
3. The DL label shown in Context Help
4. A possible mechanism to show the DL label on the BD and/or the FP
The DL label should have a distinctive background colour that cannot be changed (could be any pale colour)
It should be possible to show the DL label on both the BD and FP, only on the BD, only on the FP or neither in the BD nor the FP
Screenshot 4 shows a possible mechanism to show/hide the DL. There may be better mechanisms out there.
Selecting a DL label on the BD or FP and pressing DELETE (like when deleting a regular label) hides the DL label on the BD or FP respectively. Equivalent to unchecking one of the checkboxes in screenshot 4.
The two settings for showing/not showing the DL on the BD and FP should be stored within the VI. The settings should be preserved when creating a 'Save as...' copy of the VI.
It should be possible to independently resize and move the DL free label instance on the BD and/or FP (the size and position of the rectangle is not synced). Notice the size of the rectangle isn't the same in screenshots 1 and 2.
The DL label has no influence on whether other free labels exist in the BD or FP. Any number of free labels are still allowed.
This idea would ease the process of creating and maintaining well-documented code
When using a subVI inside a caller VI, the Context Help documentation is extremely useful (it may be the only documentation available if the subVI is part of a PPL)
When editing or inspecting a VI, the Context Help documentation is often not at hand. What is available at a glance is often a big free label comment somewhere on the BD or FP
As the VI is edited, the big comments on the BD and/or FP inevitably become out of sync with each other and with the Context Help
The DL label introduces the concept of having a 'master' documentation source, or a single source of truth
At Renishaw UK, some of us use an in-house scripting tool that searches for a free label containing the first word 'Description' on the front panel, and copies the remainder of the text into the VI Description. It's a useful workaround, but this idea would remove the need for such workarounds, and would add the benefit of two-way syncing (editing the VI Description to update the comments in the BD/FP).
CTRL+Click on an input is a great little tool to switch the input.
However, it only works when both inputs are wired. Often (, I or QD connected a wire wrong,) I feel like switching the input, before wire-ing the 2nd. Only to find it doesn't work...
Having to connect the 2nd wire just seems to disrupt the flow, being focused on the first input. Being forced to make things worse (connect two wrong wires) before being able to make it right just feels itchy to me.
It's a minor thing, but I never understood why it would be limited to 2 wires.
One of the things that sometimes bugs me when using LabVIEW is that if you have a front panel or block diagram in a small window, many of the menu options and toolbar options are inaccessible without having to resize the window first. You have to have a minimum window size to be able to access all of the toolbar functions.
Still don't get it?
This is how big I want my SubVI window to be:
Problems with the above:
A lot of the toolbar buttons and menu options are completely inaccessible
I'm sure it was for good reason (probably some other icons that appear there), but there's also a load of empty space to the left of the run button which would allow me to fit more of the toolbar on screen
To be able to access the entire toolbar, the windows has to be at least one of the following wide:
Why is this a problem?
Normally my front panel windows are nicely sized according to the controls and indicators on the front panel (e.g. controls top left, indicators top right, error clusters bottom), for most SubVIs this usually means that the window is thinner than the minimum width to show all of the toolbar options.
If you have a fixed size UI panel (e.g. for dialogues) - if you want to align / space objects on the panel you have to make it larger, do the scaling and then resize back to the original size which isn't ideal (possibility for not resizing to the original size correctly)
Similar to the above but if you have a UI where you have fit/scale to pane you might want the initial size of the UI to be smaller than the minimum width
Just before submitting this idea I realised you can shrink the 'search' bar from the toolbar to make it slightly better
Use the OpenG (?) VI for 'fit to largest decoration - this is OK for some UIs but not really suitable for the SubVI case above
Please make it so that the menu and toolbar are accessible regardless of window size. One solution would be to have a button that allows you to 'scroll' the toolbar or have a pop-up dialogue that shows the missing toolbar buttons as per the image below.
MS Paint skills (icon lifted from Chrome's bookmarks bar):
As an aside, MS Word manages it fairly well (even though it isn't that readable), and it has a LOT of toolbar buttons:
Please consider my idea (or Kudos it) for future versions of LabVIEW - it will improve usability of the IDE.
The right click, find options are great but limited. I would like to find events that are triggered by a given control/indicator; this is hard if you have many events and some handle many triggers. Currently I have two less than ideal work arounds.
First work around is a text search. It gives a lot of irrelevant data for the results I want.
Second I begin the process of adding a new "fake" event, and guess at what type of trigger the control is using (mouse down?, value change, etc.) If I guess right and it is being used I get a warning saying it is used and the event number (golden but often off by one because it counts the case I am pretending to add). Again if I guess the wrong type of trigger I get no help.
It would be great if there were any events that were triggered by the given control, that would be added to the list of options under the right click find (and not show up if none existed like find local variables etc.)
The issue is that there are some situation where we have multiple developers using the same PC (Ex. limited number of test stations where HW/SW integration is performed). The last developer on the station changes the Environment Options to their desired settings.
To allow a developer to quickly switch to their preferred set of Environment Options, we would like a feature that would allow the following from the LabVIEW Splash Screen: (see image suggestion below)
Save current Environmental Option settings and assign that set a name.
Export/Import to from system using a file.
List the Environment Option sets currently on the system in the Tools menu
Add a new button to the search results dialog called "Set Aside" so I can have multiple search results open at the same time. Put it near the bottom just below the search results. When you click it, it changes the title of the window to "Search Results - Set Aside 1". If you click "Set Aside" again when #1 is open, it will open "Search Results - Set Aside 2" ... and so on. This way you can have several different search results open simultaneously. I love the check mark feature in the search results, but it resets every time the search windows is closed or overwritten by a new search. Thus I lose my place if I want to make sure to check every instance of something but need to search again while looking at one item.
When a string control, indicator or constant is switched from any mode other than Normal Text, display a small glyph (similar to the radix indicator on numeric controls) to allow you to see that the display is something other than Normal Text.
I'm not sure if this is a bug report or a feature request, but I think it should be fixed/implemented, all the same 🙂
If you right-click on a Boolean funtion (And, Or, Exclusive Or, Not, etc.) and replace with a Compoint Arithmetic (CA) function, the CA function is always set to the "Or" configuration. I would expect it to be smart and put the CA node into a configuration (including negation/inversion dots) that is equivalent to the Boolean function that it replaces.
Currently, when you use context help and hover over a VI it shows terminals and a little snippet of what it does. I use this a lot. When using quick drop though, the context help doesnt dynamically change to each item selected or hovered over with the mouse. Its like this currently
I would like to see it so that when I hover over an item in the quick drop, the help page updates so I can read it without having to drop it onto my back panel, read, then delete and try again. Like this
A LabVIEW application installer generated from App Builder creates multiple folders and files in the folders. It is desirable to have a single file installer so that customers see only 1 file to install.
Sometimes when dealing with the Bundle/Unbundle by Name nodes, I start with more elements than I actually end up using. Then, my block diagram looks something like the following:
Maybe I'm just lazy, but I really hate removing each unused item from the Bundle/Unbundle by Name node over and over. Right click on unused element, click "Remove Element", Right click on next unused element, click "Remove Element", etc... Ugh!
So I'm suggesting a "Remove Unused Elements" when you right click on a Bundle/Unbundle by Name nodes. With this option, right clicking on one of these nodes would look like this (emphasis added 😞
The result of this operation would look something like this:
Now I can spend my time coding instead of getting rid of individual elements! Thoughts?
It would be a small yet very welcome improvement if the 'size to text' option could be added to the enum and ring options when in arrays rather than having to manually adjust them.
Here we have a combo box vs enum in an array. Both contain identical lists which consist of the following:
Now if you right click the combo box you get the option to size to text: Right click the enum and you don't:
Also, when you 'size to text' on the combo box list, it sizes to the item you selected rather than sizing to the longest string as shown here:
Yes you could argue that it did exactly what you asked but my preference, and I'm sure others will agree, that it would be best to size to the longest string. Maybe have two options in the list. 'size to current element' and 'size to longest element'
Many times a while loop needs a delay for one reason or another, even if its just to add a small delay so the program doesn't peg the processor. Having this would clean up BDs, and it would also act as a reminder to make sure your code doesn't peg the processor. (with nothing wired to it, it would default to zero)
With 6 or 8 input/output patterns it is extremely difficult to see difference between particular I/O. This is even more problematic you use for example INT32`s or other data types that have dark color as default.
One gets few pixels of dark blue with black border around it to make things even more difficult.
- Make an Assigning Terminals mode where the icon with terminals gets enlarged eg. x4 and where all terminals are clearly visible.
- Do not add more black borders, just stick to the data type color.
- Add clear indication which controls and indicators have already their terminals assigned (general information). User by clicking can see which one is assigned to what terminal (as it is now)
If there is a "Move Up" and "Move Down" option is available for "Unbundle by Name" and "Bundle by Name", then it would be very helpful. Then, instead of deleting the removing the items and then inserting the same item in some other row, I will just move it up or down....