Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Do you have an idea for LabVIEW NXG?
Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!
Direct to PDF reporting is an extremely important feature to provide customers. It cannot be relied upon that the customer has MS Word or the like installed.
There are a couple of LV PDF toolkits supplied by developers. However, the problems with these include that they are (a) not updated or well-supported (b) buggy (c) have out-dated dependencies such as .Net 2.0 (d) restrictive licencing for deployment.
Good reporting tools are essential and NI should develop and support a direct to PDF toolkit.
There is no way to get to the GObject property of "Position" in the dialog box. Its only available via property nodes, but if you want to statically set the control position, this is a pain.
I run into this when I have multiple, similar VIs that i insert and remove into a subpanel. in order to set the controls to be in the same position across the VIs, i have to use the property node for a 1 time use.
I often want to pull elements out of an array based on their content. In a simple example, I'd like an array B that contains all, the elements of A that are greater than 0.5. A few previous posts have suggested a conditional append function on the output of a loop. Here's another possibility. Change IndexArray so that one can wire an array of Booleans to the Index input. The output would be just those elements of the input array for which the Boolean array element is true.
Another way to handle this would be to have a primitive that returns an integer array containing the indices of the true elements in a boolean array. Then allow arrays of indices to be wired to the Index input of IndexArray.
By the way, these are not really orignal ideas. They come from Matlab. Specifically, the A(A>0.5) syntax and find(A>0.5).
I assume that the LabVIEW sort algorithm is a comparison based sorting algorithm (and my guess is that they use a form of mergesort & insertionsort, and maybe better, timsort). Anyway, for arrays of integers, string this works perfectly. For clusters and classes the implementation does not work that smooth since the sorting algorithm will always sort on the first parameter in the cluster, respectivily class. For this reason it is in my opinion that the sort VI should have some kind of ability to edit the comparison on how the sort VI actually sorts. In many languages you have the ability to do this but not in LabVIEW. This would be very usefull for when sorting classes and clusters.
A example of how this should be implemented is as followed. When the sort VI has a non-standard LabVIEW datatype as input, one should be able to add a reference to a VI (or add by a menu), with 2 inputs and 1 output. In this VI the user needs to define the rules which apply to the datatype of the input. In the end the VI will output a boolean, telling if input 1 is greater (depending on which sorting algorithm LabVIEW uses) then input 2.
Therefore, my suggestion is to add functionality to a probe to provide the ability to replace the data passing through that point with the value of the developer’s choosing, either for a single iteration, or for multiple itterations.
Occasionally I have found instances where is would greatly helpful to be able to inject a value into a 'wire' for either a single iteration or for every iteration, overwriting the value that would be naturally set by the previous operation. This may be a desire to insert an erroneous value to test my code's response to unexpected values without disrupting the code that is in place, or, as I hate to admit, to recover a runaway thread without disrupting the execution of the remainder of the application and any associated, unsaved data.
For example, a while loop that has managed to miss its exit condition due to an unforeseen race condition, holding up a weekend’s worth of data collection from being saved to disk. Rather than being forced to click the dreaded Abort button, it would be nice to be able to simply force the next evaluation of the conditional terminal to be True, exiting the while loop and freeing the execution of the remainder of the application
Hi this is the first time a summit an idea, if there is anything else I would need to add to make the idea clearer I am open to suggestions. My idea is:
In the LabVIEW Core 1 - The Software Development Method it is mentioned among the design steps is the use of a flowchart and a state transition diagram. I believe it would be a great idea for the the LabVIEW project file (*.lvpj) to have a special type of file where we can create said charts or diagrams and develop them in an special environment all inside the LabVIEW IDE
It is clear from the title itself what i want to say.
are we going to see a function in the functions palette through which
we can directly view the Excel file as an array in labVIEW!!! Everytime
building a code using ActiveX and the property/invoke nodes is not
If the excel file has more than one work sheets,
then the user must be able to select the desired worksheet. It should
be able to display both 1D and 2D arrays
Also, if the Excel
file contains some graph or chart, It should scan for it and display
the same. This would be the set by the user weather the function should
search for the graph or chart. It should return the graph/ chart in
the form of cluster (in case the sheet has more than 1 graph/chart)
Attached is the pic of the proposed function with labels
My idea is about the representation of arrays in the "Probe Watch Window". At the moment you only can scroll through the values of a array/multidimensional array if you have a Probe on a array wire. If I want to know the dimension of the array I have to scroll through the whole array until a value is grayed. Because of that it's easier to build in a "Array Size.vi" to find out if my arrays have the right dimensions but it would be more comfortable if I could see it already in the Probe Watch Window at the Probe Display
In summary it would be very helpful if I could see the dimensions of a array at once in the Probe Watch Window.
The current error-case only allows two states, when the error-cluster is wired: "No error" or "Error".
My suggestion is, to allow any number of cases which depends on manually defined error-codes (see attached picture). The error-case must be enhanced so that error codes can be treated separately in individial cases.
Previouslyto handlea specific errorcode, first thecode must beread from theerror clusterand than be wired tothecase.This is to be omitted.
I've attached an image with this idea. Sorry for the duplicate posts.
These are simple examples but can get more complicated. For example, usage 2 can have more input (e.g. 4) it will have 16 possibilities which have different simplified code.
USAGE 1: User wires some input on the block diagram, when the simplify button is used, it simplifies the complicated code to a simple one ( noting that it is not the unique solution as shown in USAGE 3)
USAGE 2: If for the application, the user changes the value of the input and he gets different output; this table can get the simplified; or the "best fit" for the number of data present.
Quite often I find myself using a combination of Array Size + Index Array with a constant to know just one size of a multidimensional array. Wouldn't it be easier, if Array size would behave in a similar way as other array functions - depending on how many dimensions the array has, so many outputs show up. The example shows 2 dimensions, but could be expanded to more
In their current form, Auto-Indexing tunnels only operate on a single dimension of an array. For example. If you input a 2D array, through an auto indexing tunnel into a for loop, and display the resulting 1D array in an indicator inside the for loop as below, you will always get the last row.
I'd like to see a feature where you can right-click on the tunnel or something, and set it to auto-index by column, instead of by row, and get the last column instead.
It could be as simple as an option in the context menu for the auto-indexing tunnel to say "Index by rows" or "Index by columns" It gets more complex with 3D 4D and moreD arrays, but you could do something like a submenu flyout that says "Index By Dimension" > "1", "2", "3" etc