LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

View All (1)

Multi Conditional Tunnel

View All (1)

There is a method how to call a .exe with Parameters over the ( http://digital.ni.com/public.nsf/allkb/17C3AD70493CE0208625666A00763364?OpenDocument)

But there seems to be no Way to give a Value to Return to the cmd as ReturnValue.

In C this would be expressed instead of

void main(void)

int main (char *Args[])

{

return = x; // returns X as return value back to cmd

}

or similar.

The only way to do this now is to write a C DLL wrapper around the Exe and call this one to get a custom Return value. This is not very comfortable when you choose LabVIEW in order not to have to write in C.

Instead this should be included in the Build Specs just like with the Arguments. The Datatype and Data to be returned should be specified via Property nodes, and the Value should be passed back up to the CMD when finished.

This is handy when using Batch scripts.

Virtually ALL of my more complex typedefs have multiple datatypes wrapped in a cluster. The result? A pink wire. I have fat, pink wires all over my code.

Allow us to choose different patterns and colors for wires on a typedef. Increases the ability to spot a typedef, and allows for distinction between two complex datatypes.

(Note: I am not condoning making a new wire for every typedef... that would be a point of confusion when collaborating. I would just like to add distinction to some of my more distinct typedefs).

View All (12)

List recent files by project

View All (7)

View All (1)

This might be a bug report; it depends on whether todays behavior is intended or not(?).

Anyway: if you have properly defined the destination of a file in your application build e.g. on Source File Settings, but then later learn that the file was not actually on the list of source files - adding it to source files will automatically change the destination(!). I suggest it should check whether the user has already defined a valid destination for it and if so keep it.

Here is a demo of the issue:

Extremely small pointers in Labview

Fixed length string datatype

This has been brought up long ago, but I thing it deseves to be discussed here in the Idea exchange.

There are situations where it might be beneficial if we could have a string datatype that has a defined length. Arrays of such string would be stored flat in memory.

Application would include:

Typecasting a long string to a string array where the element is fixed length would slice up the string into an array of equal length strings.
Reading a binary file as an array of fixed strings would do the same.
...

The default value would be a string of the defined lenght filled with \00. Shorter inputs would get padded with \00

Of course certain operations would drop the length, e.g. when concatenating such strings, the length would get dropped from the result, turning it into a plain string.

Loop iteration indicator default name

View All (4)

Another request from my carpal tunnels here. When you Right-Click and Create Indicator, you get the indicator wired to the terminal you selected. When I right-click a reference and Create Property For... or Create Method For... I would like to get the PN/IN wired to the reference. Right now it gets placed on the cursor when you select the property or method, and if you are unlucky, that can be a considerable distance from the terminal. Now you have to drag it back into position, hope for autowiring to catch, or wire it up yourself. I would much rather have it placed and wired automatically.

View All (5)

LabVIEW Idea Exchange

input of conditional terminal should be "pass through."

Change (Increase) Cursor size within LabVIEW

View more information in the column header of the projects

Multi Conditional Tunnel

Ctrl+Click while wiring change the cable source

Error Description for Error Ring Custom Error codes should be searchable

Return Value of LVbuilt.exe called in CMD with Params

Allow Typedefs to have a User-Defined Wire

List recent files by project

Add "Akima Spline" option to the existing interpolation functions

Allow copying of FP and BD elements from locked VIs

Implement "Duplicate Frame" method for DisableStructure class in VI Scripting

Make LabVIEW look nice on a retina display

Do not change VI Source File Setting when it is added to build source

Copy and Paste elements in Cluster

Extremely small pointers in Labview

Fixed length string datatype

Loop iteration indicator default name

Autowire Property Nodes Created From Right-Click Menu

Add more options for the Pane properties dialog