LabVIEW Idea Exchange

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

It would be a small yet very welcome improvement if the 'size to text' option could be added to the enum and ring options when in arrays rather than having to manually adjust them.

 

Enum vs Combo box.PNGHere we have a combo box vs enum in an array. Both contain identical lists which consist of the following: Enum List.PNG

 

Now if you right click the combo box you get the option to size to text: Combo List Option.png Right click the enum and you don't: Enum in Array Right Click.PNG

 

Also, when you 'size to text' on the combo box list, it sizes to the item you selected rather than sizing to the longest string as shown here: Combo Box Not To Longest String.PNG

Yes you could argue that it did exactly what you asked but my preference, and I'm sure others will agree, that it would be best to size to the longest string. Maybe have two options in the list. 'size to current element' and 'size to longest element'

 

 

Regards

 

Mitch

First of all I know this may sound crazy, but I do have a specific use case (2 actually) and I think it generalizes well.

 

Use Case

Caraya uses a Quickdrop shortcut ctl+u to run all unit tests in your project. I have a quickdrop shortcut that I use to run VI Analyzer on just the files that have changed in Git.

 

Both of these shortcuts are incredibly useful. However it requires having a VI open. There are often times when I just have a project open and want to use one of these shortcuts. For example when I first open a project, I often want to run the tests first thing. I realize you can add these type of things to the tools menu, but then I have to memorize 2 different ways of doing something depending on context. It would be much easier to use the QD shortcut here.

 

I realize  that QD is typically used for dropping objects (on the bd and fp) and that doesn't really make sense from the project. But these shortcuts (and I'm sure there are others) don't rely on that functionality. Also you could adapt QD to act on highlighted project items or allow you to "drop" a new VI or class or library or something.

 

I mentioned it to Darren and he mentioned it would require the C code changes to allow the project window to capture the ctl + space event. The project window already does handle some ctl key events. Apparently ctl + space seems to be unhandled. I'm sure there is probably more to this idea than simply that, but I feel like it is worth exploring.

If there is a "Move Up" and "Move Down" option is available for "Unbundle by Name" and "Bundle by Name", then it would be very helpful.  Then, instead of deleting the removing the items and then inserting the same item in some other row, I will just move it up or down....Smiley Happy

 

Idea Exchange.png

Compare the upper loop(old) with the lower loop(new).
Take a close look at the loop exit.

 

 

Solution: Right click the indexing tunnel and select "Enable Conditional Append"

This works not only with FOR-Loops. 

 

History: This idea was already presented by me in May 2008 http://lavag.org/topic/7574-conditional-append/page__p__44719&#entry44719 

Breakpoints are great for debugging.  But...I've never wanted to share them with another developer, and I've never liked it when they add the dirty dot to code that I haven't otherwise changed.  This can lead to unnecessary code changes which can add hassle to source control, and it can lead to other developers unintentionally inheriting your debugging breakpoints.

 

How about an option to manage breakpoints separately from source code, perhaps similar to how compiled code is handled?

tkendall_0-1645203581030.png

With more than 1000 classes in our main project it is impossible to find a class to inherit from, a simple search function would be great. 

 

Please support partial matches, case insensitivity and regex. 

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).

In my block diagram, I may place a cluster by icon on a bundle by name. If I (right click) to replace that cluster with a different cluster, the new cluster is fully exploded. This explosion can cause my structures to resize to accommodate the new cluster. I would like for the new cluster to be it's icon (if the original cluster was an icon).

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

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

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

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.