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 am struggling (yet again) with LabVIEW installation problems that appear to involve LabVIEW 2017 (and possibly LabVIEW 2016 f5 patches). After having systems with multiple (sometimes only 2) LabVIEW Versions installed "go south" (typically by having MAX stop working and Block Diagrams with DAQmx code fail to load), I've tried to "Remove All" NI software, only to discover that "bits and pieces" still remain, both on Disk and (especially) scattered throughout the Registry.
I've been working with NI Support for 2-3 weeks trying to "recover" from a LabVIEW corruption probably caused by installing the 2016 f5 patch. We finally decided to do the "Uninstall/Reinstall" route. Although I got 2012 SP1 installed, 2014 SP1 failed (could not install NI Network Discovery 14.0, "Verify you have sufficient privileges to install Services").
My concern is that, short of reformatting my hard drive and reinstalling Windows (which I was forced to do on two of my PCs), there appears to be no way to fully uninstall all NI Software. I would like to propose that NI develop an "Eraser" utility (like Eraser for Microsoft Office) that searches out all files that NI puts on the C: drive (not in User Space) during installation and all Registry entries that it scatters throughout the Registry, allowing the PC to be "rolled back" to a "pre-NI" state. Such a tool might want to be restricted to Full or Professional licenses, or maybe provided on an "As Needed" basis by the NI Support Team, but I really don't want to have to rebuild yet a third PC ...
Unfortunately, the minimum size of these elements is 5 pixels , making a 256 element color ramp 1280+pixels wide, showing redundant information in 5 adacent pixel columns each. If we display the color ramp vertically, it would not even fully fit on a common 1080p display!
This makes it too wide to correctly display them in the forum and forces a size reduction that makes all other text and diagram code illegible.
(Yes, we can right-click...open image in new tab, and click the image to display it 1:1 (in chrome), but that's more work and not everybody knows that)
It would be perfectly OK if we could make these elements only 2 pixels wide (or high), making the array display a much more reasonable 512 pixels and keeping the front panel to a more reasonable size.
The minimum size of the classic colorbox (frameless) should be 2x2 pixels (or even 1x1?) Currently it is 5x5, i.e. too big.
I have VI's and projects saved in Chinese characters and they do not open in the English version of LabVIEW. LabVIEW is unable to read special character unless I change my system languages. I feel that LabVIEW should be able to read all different languages and not required to download different versions.
Have you ever auto indexed out of a while loop but had to use "Delete From Array" because you didn't want the last element? Sometimes I don't want the element from the iteration with the stop condition (behavior similar to a true "while loop" rather than LabVIEW's "do while".
I'd like a right-click option on the autoindex terminal to not include the last element.
I spend time making the size of my front panel and block diagrams fit my code well. Unfortunately everyone once in a while I will hit ctrl+T when I'm trying to press ctrl+R to run my code, and it of course changes the dimensions of my windows. I try to undo the operation, but it does not work properly (or as I would want it to). It moves it back to its position, but the dimensions are all wrong still. Very frustrating.
I propose that Undo reverts the panels to their pre-tiling size.
Auto wire is very convenient most of the time. Sometimes, however, something like this happens:
To avoid that, you either need to place the second node very far away and move it back, or manually delete the wires, which can be a pain. Especially considering you see the wires it's going to add while you're dragging it, but have no way to tell LabVIEW you don't want them other than deleting them manually. It would be nice to be able to hold a key down to temporarily disable this feature.
But what if you don't notice it's going to place a wire until you've already placed it? There should be a key for that too. If there haven't been any edits since the last time something was auto-wired, you could just press a key and the last auto-wire would go away. A good way to do this would be to just have the auto-wiring count as a separate action in the undo buffer, so you can hit Ctrl+Z once to get rid of the wires, and again if you don't want the object you placed at all.
Remark: This example is using the numerical-double-data-type but it is valid for all other data-types, too. I'm using LabView 2011SP1 (german)
Creating a reference from a numerical-control is not new and very easy to do via the context menu. But I'm missing a similar function to create a double-control from a double-reference / double-reference-control.
This would be very helpful especially when there is a VI that requires a reference to a special data type as input and you need to create a control of exactly this datatype.
As already suggested in an other idea here in this board it would also be helpful to have a context menu entry that allows to create a reference control from a numerical control without make the detour with a reference in the block diagram.
I imported and pasted a graphic (my company logo) onto the front panel of my VI, but apparently there's no simple way to resize it while constraining the aspect ratio (e.g. resizing it proportionally).
I'm not asking to do it programmatically; I'm asking simply about resizing it to fit the rest of the front panel's design.
If I grab the handles and drag, it allows arbitrary resizing on both axes. If I hold down Shift it constrains it to resizing the vertical axis only. I've tried every combination of modifier keys, on both OS X and on Windows, and I can't seem to constrain the aspect ratio.
Most other applications that allow image resizing offer one or more of the following:
Holding down a modifier key (typically Shift) while dragging a corner resize handle forces proportional resizing. The current behavior in LV makes no sense. Holding down Shift forces a vertical resizing only, but this can be done by dragging the top/bottom handle (e.g. not a corner handle).
In the Set Width/Height dialog, have a checkbox to Preserve Aspect Ratio. If checked, any entry into height or width causes automatic calculation in width or height OnBlur.
In the Set Width/Height dialog, support entry by % or by pixels, with the same option to constrain.
This will help all of us produce more professional-looking applications.
I remember this in previous (pre-8.2) versions of LabVIEW - not sure why it was removed. I have a use case to use projects as templates (like when someone wants to write a plugin for a utility I've written, I want to be able to send them a zip containing a project, methods, etc). The project includes installer settings (so their files go into the right place under my util's plugins folder, but when they build and try to install their plugin, they get an error if another plugin bult using the same template has already been installed. This is because the "Upgrade Code" (stored in the lvproj file) is the same (it tells Windows that the two products are the same, so subsequent installs are seen as upgrades or replacements, not new installs.
My memory tells me that I used to be able to hit a "Generate" button somewhere which would give me build a new code - all I'm asking for is that back (I can add a step in my work instruction to hit that button before you build).
I don't currently have a workaround for this (other than having engineers manually edit the lvproj file) - if anyone has a better idea, I'd love to hear it for the interim!
While browsing through Property Nodes, I would like a visual clue that a node is Scripting. It's great that the nodes are light blue, but only once they are placed on the BD do we know that they belong to Scripting.
Ideas might include:
1) Glyphs next to each node in the list, but I am concerned how these adornments might slow down the pop-ups.
2) Ordering the Scripting nodes at the bottom of the list, below a line that reads "Scripting Nodes".
3) Easiest: Indicate that a node is for Scripting in the Context Help, as shown below.
I would often like to directly compare numbers within an array control stretched vertically and with fixed-width font and have tried in vain in the past to include the sign of the number automatically so that alignment is not lost between psotive and negative numbers.
I'd love to be able to display the sign always (+ and -) so that I can maintain constant number width in my displays.
The digits under the long fgreen line SEEM to be the same decimal palce, but they are not. The shift due to the sign is hard to spot and makes a cursory glance insufficient to distinguish numbers from each other.
I know I can get this done using minimum field width and padding with spaces but why can't I just show the sign?