LabVIEW Idea Exchange

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

The situation:

There is a user interface that provides the user with an array control.

The array control provides the user only one or a limited number of elements.

The user must use the scroll bars or the index control to select the correct element that he wants to modify.

 

The problem:

The user can scroll to a position beyond the last available array element and enter data. This increases the size of the array as expected, but not as desired in the given situation.

After the user finishes entering, the program must check the size of the array and reduce it again.

The proposed solution:

There should be a "max. array index" property of the array control. It should prevent the user from scrolling to a position beyond this maximum element index and/or editing such a position. It should also prevent adding elements via the right-click menu when the maximum number of elements has already been reached.

 

Extensions:

There could also be a minimum property that prevents the user from deleting array elements so that the total number falls below the minimum.

 

Notes:
The proposed solution should only affect the user's input capabilities. It should not change the size of the array if it was specified programmatically.

I'm not sure if this is a bug report or a feature request, but I think it should be fixed/implemented, all the same 🙂

 

If you right-click on a Boolean funtion (And, Or, Exclusive Or, Not, etc.) and replace with a Compoint Arithmetic (CA) function, the CA function is always set to the "Or" configuration.  I would expect it to be smart and put the CA node into a configuration (including negation/inversion dots) that is equivalent to the Boolean function that it replaces.

 

Replace with CA.png

What is wrong with this VIs diagram?

 

Broken arrow.PNG

Nothing! It's a broken dependency:

Broken dependancy.PNG

 

It would be nice to see the difference without having to open the error dialog:

 

Broken Dep.png

 

Graphics should be improved...

 

The normal broken arrow should have priority over the other. First fix the VI, then the dependency... Wouldn't mind two icons, one for broken VI, one for broken dependency.

I use Error Rings for custom errors and I love it.  Being able to reuse existing codes but give addition information, or using extra string or numeric inputs makes my code more compact and readable.  But one thing I noticed is that if I perform a search in LabVIEW, it won't look at the text in the Error Ring.  Here is an example.

 

Error Ring Search 1.PNG

Even though my Error Ring contains the text "table" and it is even shown in the node, the LabVIEW search returns nothing.  There are times that my users get an error and they send it to me.  Then I will search for that text in my project only to find it isn't there.  But it is actually there, just hidden away inside the XNode that is the Error Ring.

 

Can we improve the LabVIEW search function to search inside Error Rings?

I quite often find myself wanting to change the look and feel of front panels items. You currently have to do one at a time. Would be great to be able to highlight all of the Booleans and change what they look like in one go ( Similar to how we can change the size of other properties).

Many times a while loop needs a delay for one reason or another, even if its just to add a small delay so the program doesn't peg the processor.  Having this would clean up BDs, and it would also act as a reminder to make sure your code doesn't peg the processor.  (with nothing wired to it, it would default to zero)

Built In Delay into While Loops.png

Sometimes when dealing with the Bundle/Unbundle by Name nodes, I start with more elements than I actually end up using. Then, my block diagram looks something like the following:

 

bundle by name with unused elements.png

Maybe I'm just lazy, but I really hate removing each unused item from the Bundle/Unbundle by Name node over and over. Right click on unused element, click "Remove Element", Right click on next unused element, click "Remove Element", etc... Ugh!

 

So I'm suggesting a "Remove Unused Elements" when you right click on a Bundle/Unbundle by Name nodes. With this option, right clicking on one of these nodes would look like this (emphasis added Smiley Wink 😞

 

remove unused elements.png

The result of this operation would look something like this:

 

BAM.png

Now I can spend my time coding instead of getting rid of individual elements! Smiley Happy Thoughts? 

It would be nice if the format to string would support arrays.
Something like this:

MikaelH_0-1760513019416.png

 



The context help for this large typedef would be more readable if the nodes were collapsible like the XML viewer for Internet Explorer.

 

nodes.JPG

Compound arithmetic allows you to invert inputs or outputs. I find myself often checking for a string or path to NOT be empty. It would be nice to be able to invert the output the "Empty String/Path?" function instead of needing to wire up the additional "Not" function. It would look kind of like this:

Empty String Path NOT.png

Thanks!

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

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 

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

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?

When wiring to a growable node that is currently full requires you to either pull the node bigger first and then wire or wire and create a wire stub, then pull it larger and the Connect the stub to the terminal. 

Instead change the behavior so, if wiring is started and ends over a growable node, the node will grow automatically and add the wire being created to the new terminal. 

For example: starting an error wire and ending on a merge that is currently full, the node automagically grows by one and adds the wire to the new (last) terminal. 

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