LabVIEW Idea Exchange

As I am posting this, I see the NI "New Idea" page font bar shown pretty much like the one I am suggesting.  I think it may be time for NI to place this style of selection on the top of their FP and BD.  This suggestion is in addition to "A better way to specify (default) fonts", by Altenbach.

When designing larger user interfaces often times my event structure ends up with many cases sorted in no real order. Commonly there are multiple controls that trigger the same event case. It is cumbersome to try and find the particular event case where a control is handled.

 

 

What I would like to see is a Find -> Event in the shortcut menu for a control. We can currently search for the front panel control, local variables and property nodes if used. It seems logical that events should be included in that list as well.

 

Please implement a way to generate reports in ODF (native format of OpenOffice) as it is a file format everybody can read (.doc is not because you must buy Microsoft software).

 

 

If you do that, programmers will automatically be able to generate PDF because OpenOffice has a dos command to convert any ODF document to PDF.

When creating complex UIs with a lot of controls on the front panel, it is difficult to find the control we're trying to associate an event with from the Edit Events dialog, as controls are not sorted alphabetically. It seems they are sorted in the order we create them. Sorting them alphabetically would improve our efficiency as it takes more and more time to find the control as rthe UI grows.

 

I was going full speed programming block diagrams, and, of course, not stopping to put any documentation in the block diagram, and I just got this idea:

Wouldn't it be cool if you could drop an emoticon, similar to what is done in a written manual (a circled question mark, triangular warning, etc.) into a panel or block diagram, which when operated, opens an info pop-up, or links to a paragraph in the VI info or to a help file?

If I'm the first to post this Idea then I'll be shocked.

The Idea is simple. We all love programming in LabVIEW, and I'm sure that we've all at one time or another had a colleague, friend or family member ask if we know how to do something on the PC. The immediate thought is I don't know where to get the software to do that, but I could write a simple LabVIEW app  in a few hours that does the job.

E.G hunt through someone's PC and move all of the jpg files over a certain size to a specific location so they can easily find their holiday snaps.

 

You can't create this simple function for them, because if you do, and build an exe, they still need the Runtime engine.

 

Surely for REALLY simple stuff (File IO, basic comms stuff in the Base LabVIEW edition ...) - not DAQ or anything like that it is possible to create an EXE that INCLUDES the runtime components that it needs and is stand alone.

 

This would open up LabVIEW for the use of making quick gadget like apps for the office as well as test and measurement.

 

I can't se how this could be a bad thing.

Add an  option in the installer build to run cleanup-programs during uninstall.

 

On the advanced tab in the Installer build there is an option called: "Run executable at end of installation", but there is no such option for the deinstallation.

 

We use the existing option to run a batch file that installs and starts the application as a service. If the user decides to uninstall the application we would like to run another batch file to stop and deinstall  the service - but there is no option to run an executable during deinstallation.

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

Sometimes, the case selector label gets in the way of wires.  It would be nice to be able to drag the label left or right.

 

 

 

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)