LabVIEW Idea Exchange

Community Browser
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW 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 Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
cancel
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!

Post an idea

Here's how we currently make cluster element labels appear, and a proposed idea for improvement.

ClusterLabels.png

I sometimes use arrays of classic frameless colorboxes to quickly display a color table.

 

Unfortunately, the minimum size of these elements is 5 pixels Smiley Sad, 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.

 

 

Idea summary:

The minimum size of the classic colorbox (frameless) should be 2x2 pixels (or even 1x1?) Currently it is 5x5, i.e. too big.

 

 

An Image worth a thousand words Smiley Happy

 

ErrorRingImprovement.png

 

Thank you

 

Dany

 

Smiley Wink Only single click to concatinate 1D array out from For Loop:

Concatenat For Loop output tunnel.png

 

 Usually we can make it like below Smiley Sad.

 

But which easier, faster and most elegant Smiley Happy.

 

Concatenat 1D Array via shift register + Build_Array in For Loop.png

If you configure a plot to use both left and right axes, the little dash marks can be mistaken for negative signs on the right axis:

 

plots.PNG

 

In the above example, the right axis ranges from +80deg to +120deg. But it sure doesn't look like it!

 

Can we have an option to turn off those dashes? Or change the symbol?

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.

 

references.png

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.

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.

 

Upgrade Code.gif

 

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.

 

 

 

ScripNoce.png 

SR2.png

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.

 

nonuniform number formatting.png

 

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?

 

That's all.

 

Shane.

Could i sugest that two new tabs be added to the NI Idea Exchange web page to further separate out  from the now large, 266 pages of ideas, those that are:

a) Declined ideas

b) Implemented  / completed Ideas

This, i believe, returns the group focus to only those new sugested ideas. (not a mixed basket idea listing) 

 

find.png Arrow.png PE.PNG

Some times it is not easy to find the actual edited vi in the project window.

I would recommend to add an additional entry in the icon pop up window (front panel and block diagram window) that finds the actual vi in the project window.

It should:

  • open Project window and brings it in front,
  • jump to the actual vi in the Items view ad selects it

Something that I think got lost in the newer versions:

You copied a code snipped , switch to your block diagram and paste the code. 

Currently (8.6.1) the code will show up highlighted in the center of the screen and you have to move it where you think it belongs.

 

I want to (right) click on a position in a diagram, hit Ctrl-V  and the code show up at the click position.

 

 

I think it was there in the past, however I didn't found something in the options to turn that back on.

In some cases, it would be very useful to be able to copy and paste the text of the selection box.

 

QD Copy Paste.jpg

If the Label Position is changed from default position there should be the option to retain the position, because finding the label in a very huge block diagram code is difficult as label is the only identification for the item

In my experience, it is common to open files written by other peole, and realize that constants are displayed in hex or bin format only after spending time in debugging.

 

I think it would be nic to see directly on the block diagram the display format.

This could also apply to controls/indicators.

 

 dispFormatHint.png

I don't really expect this to get implemented because there are things far more important out there. But, I'm going to post the idea anyways. When creating a new VI, the default icon puts a number in the lower right corner. I have never used this number. I immediately delete it, grab the background color then dump paint to fill in the layer that was removed. You wouldn't think something this little would be so annoying, but it drives me nuts. I am curious if anyone else has similar sentiments?

 

This is especially annoying for classes because despite designing a default icon for the class, I still have to modify the default on every VI to remove the number!

Every so often I want to pop up a VI at my mouse location when I click a control. The annoying part is the coordinate system from the event structure is relative to the pane. The position property node is relative to the front panel window. But I need coordinates relative to the screen. It is doable to get the appropriate coordinate system but it would be faster if you can just choose which origin you want (pane, front panel, screen).

 

I thought it could be an input on the property nodes like in the image below. The input can be an enum with the appropriate options.

Position Origin.png