LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

As mentioned here long ago in another discussion, I really dislike the option Auto-insert Feedback Node in cycles.

 

Let me quote my old opinion here:

 

"Which I think should NOT be the default behavior: It "fixes" potentially incorrect code by throwing even more potentially incorrect code at it. I can't remember a single instance where I wanted that behavior."

 

While I wish this option would disappear completely, I think at least it should be off by default.

 

There are plenty of examples (e.g. here or here) where an auto feedback node insertion covered up a serious dataflow issue by making the VI no longer broken. This is a disservice to the new programmer who might not even understand what a feedback node really does.

 

A feedback node needs to be intentionally placed in all cases.

I often use the "most recently used" files/projects feature when working with LV. But i have no option to remove files/lvproj's from this without modifying my LabVIEW.ini-file.

I would like to have a method (e.g. right-click menu) to remove entries from that list.

Most recently used.PNG

 

To further expand this idea: Why not evolute the "recently used" section to a "bookmark&history" section where i have full configuration capabilities?

Hi,

 

when you right click on a color property node, and select create constant, the result is a U32 constant !!! Smiley Sad

so that you have to know the representation of your color in U32 formats, or you will replace it with a color constant.

 

I think it will be nice when I create a color constant to create a color constant not a U32 constant.

 

dd.pngsss.png

 

Within LabVIEW Build Specs you can specify a version for an executable that is built.  You can presently see this from within the Windows add/remove program and there are some funky ways of getting this version with .net or WinAPI calls but you should be able to do this from LabVIEW similar to the app version as shown below.

 

appversion.JPG

 

This should also be within LabVIEW so that it can work from LabVIEW Real-Time as well.

The title says it all - I'd like to have the option to inherit my configuration settings from the previous LabVIEW installation (or from a specified path).  Currently I have to do this manually by copying the ini file from the previous version, but I'm never sure whether there will be compatibility issues with the new version of LabVIEW or if there are obsolete settings.  The installer should check for compatibility/obsolescence issues as it creates the new ini file.

 

Alternatively / additionally, I'd like to be able to specify where LabVIEW loads the LabVIEW.ini file from (which could be located on a network or USB disk).

Many of us would have experienced situation where we would like to have listbox indicator or control as opposed to using array of cluster. For eg.

 

listbox control..PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This is achieveable with the help of array of clusters containing different control.

 

array_of_cluster.PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To some extent dropdown menus can be implemented in listbox, but with with large and complex codes with property nodes.

It would be great to have listbox control / indicator which would be simple to use like cluster element; as in below.

buddle_by_name.PNG

Such a listbox element is very useful in product testing application.

When  we are resizing the window if it shows the size means it will easy to make User interface as shown

Resize window shows.png

Currently, if you want to enter in multiple elements in an array, you have to click on the empty element before typing.  It would be more effecient to be able to press tab to enter another element in that array.

LV2010 introduced a new possibility of accessing class private data via property nodes. However, I suggest to reduce the size of the property node when the Name Format is set to Short Names (default). The suffix .lvclass is not necessary.

 

24582iAED03877045EE9C1

Provide a method to delete a shortcut to a recent file that is no longer current. The main LabVIEW window on the right-hand side below Open Existing has a list for All Recent Files, Recent Projects, Recent VIs, or Other Recent Files. The All Recent Files is default and perhaps most convenient. However, it always lists projects before files. Therefore, if we open numerous projects the recent files are pushed down and must be scrolled to, limiting convenience. It is common to open an example project, a new Untitled Project 1.lvproj, or one to help a coworker. These take up space which could show frequently-used files. These can be deleted from the LabVIEW.ini (e.g. RecentFiles.projectPathList, RecentFiles.pathList keys) but doing so it tedious and prone to allow accidental changes. A right-click pop-up menu could contain a Delete/Remove from List item; the Delete key cannot be used because there is no item selection since a single click opens the item.

The useful feature of having an arrow connect a free label to the part of the code it refers to was added in LV 2013. However, there are cases where a label refers to multiple objects, so you would want to point an arrow to each of those objects. Currently this is unavailable. I suggest that this feature gets implemented in following LV releases. It makes block diagram documentation just that bit better.



Attached Labels Now/Future

Hi all,

 

It will be very convenient to have the ability to change the amount increment in a for loop.  Currently, the i in for loop start at 0 and increment by 1 for each iteration.  It will be great if we can change the start point of i and the amount increment, similiar to what we can do in c.

 

for(i=2; i<10; i=i+3)

 

Yik

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.

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.

I find it a real pain to add simple formatting to text in labels and decorations (free labels / floating text).  I really wish that Ctrl+B (Bold), Ctrl+U (Underline), and Ctrl+I (Italics) would do thier expected magic.

I suggest having a feature that would allow us to add "virtual" error terminals to any VI by right-clicking any VI and selecting "Add Virtual Error Terminals...". These virtual terminals would do nothing more than act as pass-through tunnels to facilitate data flow. This would allow us to minimize the use of sequence structures:

 

Example

The thumb tack in the palette is handy. But it disappears when we right click a node to find the corresponding palette.

menu2.png

So there has to be extra steps when I want to find more relevant nodes. What I really want is adding the thumb tack to it as in the normal palette, like:

menu3.png

Thank you.

 

Best wishes,

Bo

 

Have you ever wanted to place a probe on a loop iteration counter? I can't tell you how many VIs I have with a wire from the iteration counter to the loop boundary just so I can put a probe there (Maybe a pop up iter. count would suffice). Or probe an output terminal on a VI that is not wired. I know you can open the VI and put a probe on the wire but..

 

There are probably more cases.

 

Minor issue, but since we have a chance to ask..has been bugging me for about 20 years now.

 

 

In LabVIEW if I want to use a property/method of a control I have to right click and select property. Same for second control I want to use same property I have to do same operation again. My idea is if we select all the controls and right click, some common property like value, visible and etc..... Should display and by selection it generate automatically. This can reduce my application development time.

 

 

Multiple Control Selection.png

 

So if this key feature is there in LabVIEW we can select multiple controls or properties and perform some basic operations to reduce our application development timing.

 

Thanks and Regards
Himanshu Goyal | LabVIEW Engineer- Power System Automation
Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
It Only gets BETTER!!!