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

Closing the front panel (FP) of a VI also closes its diagram. But, in opposite, the FP remains open when the diagram is closed.

 

Sometimes it would be very useful to simultaneously close the FP of a VI when closing its diagram.

This would avoid to either switch to the FP (Ctrl+E) to close both windows from it or the need to close the FP separately.

 

Could this be implemented by the Ctrl+Shift+W keyboard shortcut and a Shift+Left click on the close button of the diagram window ?

If we have a horizontal axes (x-axis) scroll bar, why not a vertical one (y-axis)?

 

When doing plots for geological logs the vertical axis is used as a depth scale and users always scroll in a vertical direction. I had to improvise this in LabVIEW and it took alot of code to handle the rapid successions of scroll bar change events that get generated if a user uses the generic labview scroll bar to scroll a chart.

 

Anthony L.

When I right-click a Control or Indicator on the FP or BD, and select "Create / Local Variable" I always get a Writable Local Variable. This makes senser for an Indicator, but not a Control. It seems to me that if I create a Local Variable from a Control, it should default to being Readable, so I can wire it immedatley (rather than forcing me to "Change to Read" every time). Phil.
dsloan

Add row headers to single column listbox

Status: New
by Member dsloan on ‎04-18-2013 12:12 PM

Why don't I have the option to add row headers to a single column listbox?  I can add a column header - and there is only one column.  It is often very helpful to show the row number in a listbox and there is no easy/good way to do this for a single column listbox

Most of the new LabVIEW users will start programming from the scratch. They really find very hard to understand from where did this particular object (function) came from. So if the location of it is displayed in the context help it will give a better way to easily find that object from the location.

 

Ex: "Create User Event" can be displayed in context help as below

 

Location: Programming->Dialog&User Interface->Events->

 

(or in a shorter form that everybody understands).

 

Sorry if this idea has been discussed before. Or its not at all needed. For a newbie this will help definitely.

heel

IMAQ VI's should support all image types which makes sense

Status: New
by Member heel ‎03-17-2010 08:31 AM - edited ‎03-17-2010 08:33 AM

Inconsistency is found in the supported image types for many IMAQ vi's:

 

For instance IMAQ ROIProfile, IMAQ LineProfile and IMAQ LinearAverages supports U8, I16 and SGL format but do not support U16 format images.

 

But, a profile along a line drawn in a U16 image should make as much sense as in an U8 image. Shouldn't it? So why is it not supported?

 

In addition, I would expect it to be easy to add an additional polymorphic U16 version.

 

These are just a few of several examples of similar inconsistency in IMAQ vi's.

 

 

Message Edited by heel on 03-17-2010 08:33 AM
Maciej_Antonik

Save all project as one file

Status: New
by Active Participant Maciej_Antonik on ‎09-16-2009 03:06 AM

Most of applications we write in LV are contained inside of a project. Saving it to disk creates a lot of files (.lvproj, .vi, .ctl, .aliases, etc) and subdirectories. This is convenient when you want to copy one VI or control to another project, but very inconvenient when sending this project to someone. In this case you have to create an archive to put everything together. Make an option to save all items contained in a project in one file.

 

Making a Windows Explorer plugin to automatically open such files as directories would be also a nice addition in this case.

 

Thanks

GuessWho

LabVIEW Web UI import from VI

Status: New
by Member GuessWho on ‎11-01-2011 07:48 AM

Suggestion for developers of LabVIEW Web UI:

We would like our Web UI to have a very similar look-and-feel to the core application it is tied to.  To facilitate that, it would be useful to be able, in WebUI, to be able to point at a VI and say "import panel" - the tool would then import all sensible importable features of the VI's front panel, as a starting point.

Blair Smith

Presently i use the below mentioned snippet for calling a SubVI (with UI) for it to be a part of the Main VI (like an excel sheet) so that i dont see multiple windows in the desktop tool bar.

 

"Creates a Child VI into the Front Panel of the parent vi. Child and parent vi must already be loaded into memory.

Created by: Jack Hamilton
JH@LabUseful.com
6-25-2003"

1.png

 

The idea here is to include a option the VI Properties to add this option something like this

 

untitled.GIF

The numeric controls can be configured by specifying Min/max values ... and behaviour when going over these limits (Coerce, ignore ... )

 

This feature works fine on the front panels ...

 

But when you modify the value of such controls programaticaly using a property node ... these constraints are not taken in account.

 

It would be nice to apply the MIN/Max limits also to the "value property" (and valus signaling too)

 

 

 MinMaxNumericControls.PNG

Guruthilak

iCON MANAGER

Status: New
by Active Participant Guruthilak on ‎03-22-2011 01:53 AM

I am not sure whether something similar has been propoesed or not..

 

This is something to do with the ICON EDITOR...I propose a "ICON Manager" (see Endevo ICON Manager) with which it should be possible to apply the icon to all the vi's/ctl present in the directory or llb.

 

-->The Name of the folder or the first name of the vi (ex: If the subvi name is "abc_xyz.vi", then "abc" will be the header and "xyz" would be the body) can be used as the header. (or automatically find the header)

 

-->An option to preview and apply the same to all the vi in the directory (whether they are linked to one another or called dynamically should not matter)

 

-->An option to select the Main (toplevel) vi and apply the icons to all the calles

 

 

pachook

Allowing proxy settings for LV

Status: New
by Member pachook on ‎08-27-2010 03:25 AM

At my current work place we use proxy servers as an internet connection. With LabVIEW it makes it difficult not only while the NI software is being installed (to check for updates, connect with server for veryfication etc) but also during typical work it makes troubles with finding examples and drivers from a development enviroment.

 

I would suggest adding some advenced internet connection options for proxy settings etc.

 

Another little thing with a company computers is that, even when installing NI software on a D drive it still installs some example software on C:. It makes problem when your IT limited your C drive for absolute minimum, because with huge amount of NI software the amound of "additional" data is getting bigger and bigger.

 

Regards,

 

PacHOOk

BruceAmmons

Inline VI with polymorphic inputs/outputs

Status: Duplicate
by Trusted Enthusiast on ‎03-15-2011 06:39 PM

We already have inline VIs that are compiled directly into the code, just as if you had wired the code on your diagram.  Imagine if we could designate some of the inputs and outputs as polymorphic.  We could create VIs that do simple math operations, comparisons and other stuff without having to create a dozen versions for the different inputs and outputs possible.

 

I think the outputs would have to be either a fixed type or same as a selected input.  Some inputs, such as strings, wouldn't work in many cases.  If the input wired to the inline VI was not compatible, it would just fail to compile and give you a broken wire, just as if you had wired the same code into your diagram.  It really would just be a block of code that could easily be added to a diagram as a VI, but it would be recompiled based on the inputs.

 

Bruce

LabVIEW opens the file in the version of LabVIEW that was most recently opened instead of the version the file was saved in.  Add a header to the file to allow LabVIEW to open the file in the correct version.  This will save a lot of time and lower frustration of accidently saving a file in the newer version.

The Report Generation Toolkit does not allow you to delete a worksheet (or anything as far as I can tell). I realize that it is a "generation" toolkit, but it does have modification functions such as being able to overwrite a cell. Deletion is a modification function of sorts and it seems like it is a pretty basic function. Also, figuring out how to open an existing file is not obvious. You have to use the New Report function. It turns out that you can use an existing file as the "template", but that doesn't show up in the documentation. Rename the function as New/Open, something similiar to the file I/O Open/Create functions and at least add a  note to the help file.

wd8ivl

Lock Wires to Block Diagram Grid

Status: New
by Member wd8ivl on ‎04-09-2013 09:21 AM

"Make & keep your wiring diagrams neat" is something that has been preached to me since I built my first VI.

 

One thing I think that would go a long way to help with this would be to be able to lock the wires on the block diagram to it's grid. This would keep wires equidistant from each other and give the block diagram a much neater look. This would probably mean that, if this option were enabled, the "Alignment Grid" pixel size would need to be locked, Also included would be something that would prohibit one wire from laying on top of a parallel wire.

These two would help to sort out VIs when you want to make llb plugins, to determine who goes where.

 

I'd like to right click on an item in the project explorer, and have two more options "Open private callees" and "Open public callees.

 

By "private callees" I mean: the callees that the selected VI is the only one to call in the whole project.

By "public callees" I mean: the callees of the selected VI that are called by at least one other VI in the project.

 

(I mean directly called and not dynamically of course, the developper would have of way to distinguish his VIs that are called dynymically).

 

Again, I've done it for personal purposes, here's the snippet in 8.6 for those who might like it.

 

Find Private and Public Callees of Project Item_BD.png

There are times that I wanted to use a numeric constant or control as a string data type. In order to use a different data type, I would manually copy and paste the control/constant values to another data type. Moreover, if the control or constant is an array of values, it's tiring to do a manual copy of the values. Creating a vi that would convert the data type would also take time. As a suggestion, I hope LabVIEW can include in their "right-click" property box a method of converting the Path to String, String to Path, String to Numeric and Numeric to String.

 

I don't know if this is a big thing or not. Just a piece of thought.

 

 21840iAA17F180F8660DF4

FallGuy

Case Statement slider

Status: New
by Member FallGuy on ‎10-13-2011 09:52 AM

Add slider, scroll bar, search to case diagrams.  Move slider to selection vs starting at top of list. This helps when we have a large case statement. See attached jpg file

 

Chris.Osiecki

Incompatible Runtime warning

Status: New
by Member Chris.Osiecki on ‎08-08-2009 12:41 PM
I spent some time the other day troubleshooting a problem and couldn't for the life of me figure out why my program wasn't working. By chance, the guy who'd installed the runtime engine on the computer I was installing to had left the executable on the desktop. He had used the minimum install that's normally for remote front panels. It would be great if there was a warning when you tried to run a program that needs the full run-time install but only the minimum was installed. Most of the program worked (a suprising amount actually), but it was only certain features that didn't. The features that didn't work (like TDMS logging) wouldn't throw an error either, even with debugging enabled. If there had been a pop-up warning that the program wouldn't work completely with the current run-time engine, I would have saved a couple of hours of combined time between me and the other engineers trying to run a test.
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
52
39
25
23
21
Idea Statuses