LabVIEW Idea Exchange

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

For log files, configuration files and data sheets I often want to save the current value of Enum controls.

What would help a lot is a function that converts the selected object name of the the Enum into a string:

 

Enum2String.PNG

How about a plugin for doing vi analysis to check whether our vi follows the style rules of Labview?

Something like StyleCop or FxCop for C#.

 

 

"Unbuild" would be the inverse of the "Build Array" function; the input would be an array, and the ouput would be the elements of the array. That way we can extract the items without having to go through an "Index Array" function for each element.

Hi

 

Suppose we have a big code in that a part of the code need not be executed ( still obeying the data flow).There is no option to do that .Those who are familiar with Matlab /Python  know there is acommenting option .Once commended thet statements will not get executed.The problem with LabVIEW now is in abid code if we want to try if a node need not get executed we have to delete it then claerind of wire will come.If we want to include it again we still have to do thwe same thing.If something is there ( may be a rectangle) when drawn around  a particular node keeps it away from the execution it will make development/testing  easy

 

I cannot find any way to turn off autogrow on the front panel. For example, if I put a tab control down, it autogrows to include someething that I put down. This is very annoying because I spend a lot of time trying to get things to fit to a window. The auto grow makes it so I have to constantly resize things.

 

In fact, it would be good to have a global function that turns off all autogrow.

It would be nice to have a primitive to check if a certain value is in an array. It seems like something that would exist already.

There's really nothing more to say here.

It would be nice to have an easier way to initialize simple vectors such as v1= [1, 2, 3, 4, 5], v2= [-6, -4, -2, 0, 2, 4, 6], or v3= [0, 0.1, 0.2, ..., 0.9, 1.0]. In MATLAB, this is easily accomplished as v1= 1:5, v2= -6:2:6, and v3= 0:0.1:1. No ugly for loops are necessary! Likewise, MATLAB has many matrix/array construction funcitons such as repmat() and toeplitz(). (NOTE: I am using an older version of LabVIEW: 2009 SP1.)

   I've developed a UI technique for creating highly-configurable apps that utilizes a lot of Text Ring controls to allow the user to select from a list of channels or labels or ...  I track the lists of channels, labels, alarms, etc. as the app is configured, and load the Text Rings with them so that the end user does not have to ensure absolutely correct spelling.  Then I convert the text ring to a string value before storing the configuration.  Since the list of channels is so dynamic, it is much safer to save each selected channel as a string than as a position within a list.

   The trick is that when I convert from the Text Ring to the String, I have to use the value of the Text Ring to index an array of all the strings.  Often I keep that array in a handy place, like a shift register, but at times, it is more convenient to read the Strings[] property of the Text Ring itself.  What would be even more convenient would be if there were a "Current String" property that returned the String value associated with the current Text Ring (integer) value.

I've thought for some time that the editing of icons and the glyphs available is very limited.

 

Is there any way to have a user folder available where I can place icons or glyphs that I’ve created or downloaded. That can then become available to me in the icon editor either under a new tab or in the glyphs?

For giving an elegent look to the frontpanel it,sometimes needs to be bold,coloured,justified etc:-I want to make my listbox looking elegent,for that all the listbox values need to be justify on center.I searched and came to know that we have to select each row value one by one and then go to Application Font>>Justify.It is very cumbersome if our listbox contains 50 or more datas.why don't provide an option for:-

Rightclick listbox>>Justify>>left,Right or center.

 

 

 

 

 

Using the quick-drop with a wire (typically the error wire) selected, one can insert a vi.

It would be awesome to select two wires (say the error, and a tdms refnum), and insert a single vi that consumes both wires, as opposed to creating two vis - one for each wire.

One of the many attractive things about LabVIEW, is the fact that if you can think logically, most likely, you could write LabVIEW code. However, there are lots of coding opportunities in the world, that require code that is developed in C or C++, especially products that use embedded SW.

 

Since "G" is based upon "C", I was wondering if it would be feasible to create a development tool that would allow the user to develop in LabVIEW, but also convert or create equivalent "C" or "C++" code that could could literally be inserted into a program. I've used the .dll creation utility for C developers to use in various "test" type applications, but have yet to find a way to use that method constructively for embedded projects.

I find cluster constants to be nearly unusably because the values must be specified positionally rather than by name.  What I find myself doing, and I guess this is the common idiom, is to do "create constant" to get a constant, then fill in the values using bundle by name.  I'd much rather have an option to have the cluster constant look something like the cluster control, with tips, etc.  This could be another view option, like icon.

 

A numeric control with data entry minimum of 0 and increment of 10 with "Response to value outside of limit" set to Ignore that has a value of 1 will not change (to 0) if the user clicks the control's down arrow (because it cannot go to -9).  I think it would be useful to have a "Coerce to Min/Max when within Increment thereof" added to the "Response to value outside of limit" drop down option list.  Otherwise the user may be confused and lead to believe the current value is the minimum the control can be set to.