NI Home > Community > NI Discussion Forums

LabVIEW Idea Exchange

Showing results for 
Search instead for 
Do you mean 
Announcements
We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea
altenbach

Space constant redesign

Status: Completed
by Knight of NI ‎03-11-2013 02:07 PM - edited ‎03-11-2013 02:08 PM

Currently, the space constant looks very similar to an underline character, possibly causing confusion.

 

I think the icon could be made a bit more distinctive. Here are some alternatives I just made up. I would probably prefer (1) but I am open to any other suggestions. :smileyvery-happy:

 

Status: Completed

Implemented in LabVIEW 2014

altenbach

Offcial support for the Chrome browser for accessing LabVIEW remote panels

Status: Completed
by Knight of NI ‎09-01-2013 03:10 PM - edited ‎09-01-2013 03:15 PM

As mentioned here, Chrome is now the dominant web browser worldwide, but acessing remote front panels using Chrome is still not officially supported by NI (more details and links are in the quoted thread). 

 

 

While there are some hints that several users had success back in 2010, I was not successful so far.

 

IDEA: There needs to be official NI support for the dominant browser and NI should invest some effort to get this working seamlessly.

Status: Completed

Implemented in LabVIEW 2014

blawson

Truncate Long Paths

Status: Completed
by Active Participant blawson on ‎02-15-2010 10:10 AM

I don't like the way that long file paths are shown in path controls and indicators:  If the path is longer than the textbox (and it usually is!), the user only sees the first several levels that fit.  This can be pretty confusing.

 

One way to solve this issue is to truncate the path in the middle in such a way that the filename or last folder (which is usually what's most important) is always shown.  I've seen this in other UIs and it should be a natural thing for users to understand.

 

Here's an illustration:

truncate_path_ctrl.png 

 

I think this should be a built in feature of the path controls and indicators, accessible through right-click menus and/or the properties menu of the control at edit time.

Status: Completed
Available in LabVIEW 2012
Darren

Include LabVIEW Version Number in Application Icon

Status: Completed
by Trusted Enthusiast on ‎10-13-2009 04:10 PM - last edited on ‎01-09-2012 03:34 PM by Active Participant JordanG

When you develop with multiple LabVIEW versions, it is sometimes difficult to identify which version you're using or launching based on the icon of the LabVIEW EXE:

 

taskbar.png

 

Here's my Windows 7 taskbar with, among other things, LabVIEW 8.0, 8.5, 8.6, and 2009 icons.  Which one is which?  There are ways to tell, but it sure would be easiest if the version number were overlayed on the icon.  Note the Visual Studio 9.0 icon in the taskbar...I think we should do something very similar with the application icons of future LabVIEW releases.

 

NOTE: The icon should also reflect differences between the 32-bit version of LabVIEW and the 64-bit version of LabVIEW

Status: Completed

Implemented in LabVIEW 2014

Chris_H.

Advanced Code Commenting Functionality

Status: Completed
by Member Chris_H. on ‎02-14-2011 04:10 PM

Current Situation

The current commenting practice in the BD is to place free floating comment number labels and write the comment in a text field as in the example below.

Current Code Commenting Practice.png

 

Disadvantages

- comment number labels do to stick to the code block. if the code number block is moved the comment has to be moved as well.

- no link between number and comment text block

 

This unsophisticated way of commenting LabView code lead to the lack of comments in general. Usually a new programmer can understand what happens, but not why a function is implemented like this.

 

 

Proposal

LabView provides the Advanced Code Commenting Functions.


InsertCommentBlock.png

 

CommentBlock.png

 

The comment block is more then just a text block. Basically it has a comment ID, the comment itself and a comment category.

By the context menu the following functions are provide:

  1. add comment
  2. delete comment
  3. move comment up
        The particular comment line is moved up in the comment block. The ID is decremented
  4. move comment down
         Opposite from 3.
  5. highlight function
         The function to which the comment ID sticks is highlighted.
  6. the comment category can be selected. (e.g.. Code Explanation, To Do, )

Adding Comments

Adding a comment in the comment block incorporates two steps (after selecting Add Comment from the context menu):

1. Sticking the automatically generated comment ID to a particular code block just by selecting the item the comment belongs to.

   This could be any type of code: wires, SubVIs, the whole Case, a particular Case, Sequences....

2. Writing the comment

 

 

 

Example of Block 1.png

 

If the mouse pointer is set over a comment ID the comment is shown like a tool tip and disappears as soon as the mouse is moved away.

 

Case.png

 

Advantages

  • Comment moves with function block if function is moved on the BD
  • Comment ID sticked on the BD item and ID on the comment block always match
  • generally more comments in a LabView programm through more simple way of commenting code

 

 

Status: Completed
Available in LabVIEW 2013
Hueter

Integrated Structure Labels

Status: Completed
by Active Participant Hueter on ‎06-30-2009 06:11 PM

I think structures should have a better label system. Currently I use free labels of the same color as the loop which looks great and makes the code easy to read and debug. But if I resize my loop I have to manually resize the label as well. I think this should be built into a right-click option.

 

(structure) rick-click » visible items » Structure label

 

Integrated Structure Labels.PNG

Status: Completed
Available in LabVIEW 2012

Currently, the block diagram has an endlessly useful feature. I use it every day - the Distribute Tool.

 

FrontPanelSpacingTool.png 

 

 

The following feature would be AWESOME for expediting BD readability:

 

BlockDiagramSpacingTool.png

Status: Completed
Available in LabVIEW 2011

Large string constants, like to one shown below, can really get in the way. I would like to double-click the border and have it collapse, like the LV 2010 Cluster now does. Putting large string constants in a VI, or rolling them up, are some work-arounds, but this would be easier...

 

Collapse Text.jpg

 

                                 Double-Click the "text" icon to reverse.

Status: Completed
Available in LabVIEW 2012
JackDunaway

Every GUI Programmer's Dream...

Status: Completed
by Trusted Enthusiast on ‎10-26-2009 12:22 AM

GUIProgrammerDream.png

 

...the ability to bulk-create References, Local Variables, Property Nodes...

Status: Completed
Available in LabVIEW 2012
blawson

Always Show the Connector Pane

Status: Completed
by Active Participant blawson on ‎12-03-2009 09:38 AM

My idea is simple: Put the connector pane on the front panel next to the VI icon.

 

Why: Right clicking to show the conpane means extra clicks that would not be necessary if it was always there.  It would also be solve the problem of saving the VI with the connector pane hiding the VI icon.

 


 before_alwaysshowconpane.pngafter_alwaysshowconpane.png

Status: Completed
Available in LabVIEW 2011

It'd be usefull for develloper and especially application user to improve graph control by adding to Graph direct access to Plot Visible property on plot legend.

 

For the time being, you have to go to color and choose transparent or to change visible property dynamically.

 

I propose control like that ... but we could find another idea to access Visible property.

All plot visible Selected plots visible

 

 

Status: Completed
Available in LabVIEW 2011
NelsonUWP

Make Case Selector

Status: Completed
by Member NelsonUWP on ‎07-31-2009 08:05 AM

I don't know how many times I've added a case statement post-programming, but I do know that there isn't an easy way to make a tunnel the case selector.  Usually I delete the tunnel and then drag the case selector down and then rewire, there should be an easier way.  For loops and while loops have an easy way to index/unindex or replace with shift register, why can't a case statement be the same?

Case2.PNG 

Case3.PNG 

Status: Completed

Implemented in LabVIEW 2014

DanyAllard

Boolean function accept Error Cluster

Status: Completed
by Active Participant DanyAllard on ‎06-01-2009 04:34 PM

Make possible that Boolean function accept error cluster as input as this example:

 

StopOnError.png     StopOnErrorCast.png

Status: Completed
Available in LabVIEW 2011

It could be nice to have a context help on coercion dots to see what is the expected type of the data that is supposed to be wired to. This way you can rapidly determine what kind of conversion to use to avoid the coercion dots.

 

ContextCoercionDots.png

 

Status: Completed
Available in LabVIEW 2012

When creating a subVI from a selection, LabVIEW should do two things:

  1. Use the user's default connector pane pattern instead of selecting one matching the number of inputs and outputs. This will make easier wiring and allow users to add more IO later.
  2. If the user is using a "standard" pattern (e.g. 4-2-2-4), LabVIEW should try placing the error clusters at the bottom corners and objects or references at the top corners.

It should also try to make the FP of the subVI cleaner, but that's another matter.

Status: Completed
Available in LabVIEW 2011
Edupo

Complex notes manager

Status: Completed
by Member Edupo ‎12-03-2010 04:28 AM - edited ‎12-03-2010 04:35 AM

Hello, this is my first post in this forum and I don't found ideas about this topic. I hope you like it.

 

Well, time ago I started to work with LabVIEW, It's powerful, but there are some kind of issues that I want to explain here. Now I'm get involved in a big project for a very big aerospace company, and I'm developing a complex application to acquire some data and process it. Well, this software is in development by some people and I have an idea for the work flow.

 

I explain it with an example:

If we have in every VI a little data base with some notes ordered by type or something we can read the code or we can start to work in a VI faster. Imagine that you have an event structure with several cases, and you put some notes like you can see in the following image:

 

Captura.JPG

 

Now, I'm able to revise quickly the code reading all the notes and start working only in the "TO DO" zone. But let's do a more complex design: Now I open my project explorer, and open the "Note manager" that could be like this.

 

Captura2.JPG

 

 

Here it is the real advantage of this tool: All the design are done and now I want to improve the application. Lets go only to the notes that interest to me: "TO DO" notes. If I double click on an element LabVIEW opens for me the VI centered in the zone that is interesting for me. And some more: I can check the work I've done and I can add new notes only with a click.

 

The more complex the project is, the more useful is this system. So, what do you think?

Status: Completed
Available in LabVIEW 2013
tst

Add a "Mouse Scroll" event

Status: Completed
by Knight of NI on ‎06-07-2009 01:55 AM

It would be nice if NI added "Mouse Scroll" (and its counterpart filter event) to the supported events. Today, you can do this by using the mouse input VIs in a separate loop and polling, but that's not a very nice solution.

Status: Completed
Available in LabVIEW 2013

I think it would be nice if LabVIEW was smart enough to know that when I drop a For Loop around scalar inputs it doesn't auto-index output tunnels - but rather uses Shift Registers - for matching inputs and outputs.

The common use case for this is with the Error input/output - it annoys me how it becomes an Array output.

 

As it is already wired, inline and not broken, dropping a For Loop around it should not break my code! 

 

Reference or Class inputs are other use case too - I want to pass the same thing around not create an Array

Shift registers are better than non-auto-indexed tunnels (other option) as they protect the inputs on zero iterations.

 

21826iFF181EE2E7ECE408

 

This would remove one step required for most use cases, speeding up my development experience.

Status: Completed

Implemented in LabVIEW 2014

It should be nice to limit the action of Ctrl-B to a selected part of the block diagram.

 

For the moment the Ctrl-B removes all brocken wires in the complete VI.

 

Sometime when you have a case structure with multiple cases ... and when you have multiple brocken wires in many cases ...It is usefull to keep non visible broken wires...

The broken arrow (list of pending errors) will then help you to find all locations to modify. 

 

SelectiveCtrlD.PNG

Status: Completed
Available in LabVIEW 2012
P@Anand

Display the path of the missing VI

Status: Completed
by Trusted Enthusiast on ‎07-03-2013 07:33 AM

After 2011 we have the option to ignore all the missing vi's which are missing. But after loading the project if a vi is loaded and if it has a missing vi then there is no way to check from where it has to be loaded (Expected path of the missing vi). So it would be a good option to check the Expected path of the missing vi after loading its caller (May be in the properties of the missing vi).

Status: Completed

Implemented in LabVIEW 2014

Latest LabVIEW Idea Exchange Blog Posts
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
User Kudos Count
131
72
67
63
44
Idea Statuses