Home Community Idea Exchange LabVIEW Ideas : New Ideas

LabVIEW Idea Exchange

Community Browser
cancel
Turn on suggestions
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: 
Post an idea
18 Kudos
lvABC

A LabVIEW utility for UpConvert and DownConvert VIs

Status: Duplicate Submitted by Member on 03-05-2010 10:45 AM 4 Comment
This is only a wish that NI could provide a Utility that converts a VI or Dir to Up or Down.

I had a project that was done in LabVIEW 5 (done many years ago by someone else); I couldn’t open in LabVIEW 8.6. I needed to do stage upgrade LabVIEW 7 and follow up with LabVIEW 8.6 and so on.

I understand there are cases that you can not simply down convert, because newer function may not be available in older version. In this case it OK, give user an option for force the convert and worse case the down convert VI is broken. Let the programmer fix it!

The utility should have a Status Report for convention.

Please..!
52 Kudos
Duane_Cousino

Add installation option to inherit LabVIEW.ini settings from previous installation

Status: Duplicate Submitted by Member on 03-03-2010 12:14 PM 5 Comment

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

View All (3)
12 Kudos
Sil3nc3r

Add/Remove function in shortcut menu for Index Array Element

Status: Duplicate Submitted by Member on 02-24-2010 04:57 AM 3 Comment

I just would like to have a shortcut menu option that allow to add or remove output element for Index Array Element basic function.  Build Array function already support this options for their inputs, it'll be helpfull that Index Array has the same shortcuts in order to insert or remove an output between both of them.

 

IndexArrayAdd-Remove Function 

Labels:
View All (4)
14 Kudos
jyang72211

Change Value During Debug

Status: Duplicate Submitted by Active Participant on 02-23-2010 01:06 PM 2 Comment
In text base programming, it is possible to modify the value of a variable in debug mode.  It would be great if LabVIEW can do the same thing.  This will give user more flexibility for debugging. 
Labels:
View All (1)
0 Kudos
EricC.

Exclude some folder from VI Hierarchy

Status: Duplicate Submitted by Active Participant on 02-16-2010 04:06 AM 2 Comment
I use a number of file and libraries common to all my applications.
To lighten the display would be nice to exclude certain folder from VI Hierarchy
Labels:
View All (3)
36 Kudos
JackDunaway

Show Attributes Selections

Status: Duplicate Submitted by Trusted Enthusiast on 02-15-2010 12:20 PM 7 Comment

I have noticed in some places in the LabVIEW IDE that the selected attribute is not properly highlighted. A perfect example is Cursor Attributes on a Waveform Graph:

 

ShowAttributeSelection.png

 

The currently selected Point Style and Cursor Style Attributes are highlighted with a blue box, but the Line Style and Line Width are not highlighted with the current values. This is important to know, because it is difficult to tell the difference in line widths, and could even be impossible if the cursor is off the screen.

 

I can only find these two places right now that the current selection is not highlighted, but once I find more I'll post in the comments.

Labels:
View All (3)
1 Kudos
GregFreeman

switch true false on select

Status: Duplicate Submitted by Trusted Enthusiast Trusted Enthusiast on 02-12-2010 04:47 PM 5 Comment

I would sometimes like to be able to switch the T/F cases on the select VI, the same way that you can right click a case structure and choose "make this case true/false". This would allow for less moving of things around or adding "not" before wiring the boolean up. The example here is simple, and obviously it would be easy enough to just switch things. But when you have a lot more code, it's not always quite so easy to do and can be time consuming.

 

Message Edited by for(imstuck) on 02-12-2010 04:48 PM
Labels:
15 Kudos
Mark_Ramsdale

Custom size of Images in Tree Control

Status: Duplicate Submitted by Active Participant on 02-04-2010 04:12 PM 7 Comment
I would like to see a feature where the size of the tree images can be set by the developer.
Labels:
View All (1)
3 Kudos
CJSesco

Highlight Section

Status: Duplicate Submitted by Member on 01-21-2010 02:03 PM 2 Comment

I have 2 suggestions for the highlight feature.

 
  1. A slide bar or some other way to set the speed that the highlight runs.
 
  1.  A way to only highlight a section of code but run the rest full speed.
 

Maybe it could it be done by selecting an area, as done with the diagram disable?

Or with break points. Highlight between points?

 

Most of the time when highlighting, you don’t need the entire VI to highlight just one small section or frame. So, you put in a break point before and after the section you want. When the code pauses, you turn highlight on. When it pauses again, you turn it off. On large loop iterations, this is very time consuming.

 

An example would be for nested loops. If there are 3 nested loops and you would like to highlight one small area of code in the second loop. You have to: continually wait for the inner loop in highlight, or pause-highlight-unpause every iteration.

View All (1)
3 Kudos
Manzolli

Reset the FP's relative position of the controls to the origin (0,0)

Status: Duplicate Submitted by Active Participant on 01-20-2010 05:37 AM 4 Comment
Would be nice having a way to send the (0,0) coordinates back the original position (top left of the form) moving all controls, keeping the relative position among then.
Labels:
View All (5)
3 Kudos
nate

Add Conditional Disable Options to Executable Builds

Status: Duplicate Submitted by Member on 01-15-2010 09:31 PM 2 Comment
It would be nice if there was a way to include the conditional disable option in the build settings for executables. 
Labels:
View All (2)
0 Kudos
Guruthilak

Using the "Strings" property of the Enum control/indicator for writing

Status: Duplicate Submitted by Active Participant on 01-01-2010 04:09 AM 3 Comment

Populating values to the "enum" control is not possible by using the "strings" property node and hence to populate a large data to a "enum" one has to create a "Ring" control use the "strings" property and replace that "ring" with the enum (or if you have enough time enter them manually) .

 

So why not use the "Strings" property of "Enum" to write values to it directly..See the image attached

 

 

Labels:
2 Kudos
sridar.m

Adding cases for event structure on 1 go

Status: Duplicate Submitted by Member on 12-23-2009 02:50 AM 2 Comment

Usally  we can add a event case by right clicking the event structure and adding it.

Its seems to be little time consuming if we need more cases. It would be better if we can add

all cases on single go.

 

So editor need to be modified such that we can select objects and events for each case.

 

Labels:
View All (4)
1 Kudos
Guruthilak

Probes with Radix visible

Status: Duplicate Submitted by Active Participant on 12-23-2009 02:37 AM 2 Comment
I would like to see the "radix" visible in the probes for "Numeric probes" and "hexadecimal/coded display" for "string" probes
4 Kudos
Chris_Koci

Create Coerce Primitive

Status: Duplicate Submitted by Member on 12-22-2009 01:26 PM 3 Comment

Currently, LabVIEW is great at auto-coercing data as needed with all those nifty red dots.  However, it would be nice to have a primitive to manually force coercion.  This can currently sort of be done by using a Variant to Data primitive.  However, this has the problem of not doing the error checking until run-time, when it really could be done at compile time.   Here are a couple of examples where this would be useful.

 

coercion.PNG

 

In both cases, the Variant to Data has the desired effect.  However, since LabVIEW can check at compile time whether the coercion is valid, there is no need for error wires, which the Variant to Data primitive has.

 

In the 2nd example, there are several instances in LabVIEW where it uses the name of the data on the block diagram.  In this case, you select which event you want to handle based on the name.  If I did not add the Variant to Data primitive, the event would be named "Event 2", which would be undesired (and incorrect) if TRUE was wired to the Select primitive.

Labels:
1 Kudos
CFiset

Unified View into project

Status: Duplicate Submitted by Member on 12-21-2009 12:08 PM 3 Comment
Like LabWindows, having all the Vi inside the main frame. Can desing easily all the FP, get quik access to the BD. When executing the VI, having the panel Load front as it will be in executable. Can acess to the VI FP or BD by clicking into the left tree or by the bottom tab.
Message Edited by CFiset on 12-21-2009 12:10 PM
Labels:
18 Kudos
Wim.Tormans

Select function: True case at bottom or 'invert selector 'option

Status: Duplicate Submitted by Member on 12-14-2009 02:36 AM 3 Comment

I like to keep my code tidy and aligned.

However, nearly every time when I need the select function, I 'd like to have the 'true case' at the bottom side.  Now I add an invert function to keep the code tidy.

My idea:

Add an extra select function with the True case at the bottom side or add an option to the current select function 'invert selector'.

 

AdjustedSelect.png

View All (3)
10 Kudos
RichardJennings

Probe iteration terminals

Status: Duplicate Submitted by Member on 12-12-2009 03:35 PM 2 Comment
I would like to pop-up and put a probe on the iteration terminal of loops to look at the loop count without having to wire the terminal to an indicator first.
Labels:
7 Kudos
silmaril

Conditional Disable Symbols in Build Specs

Status: Duplicate Submitted by Member on 12-10-2009 01:59 AM 3 Comment

Currently we can set Conditional Disable Symbols (CDS) for a whole project or for a target.

I wish we were able to set them inside a build spec, too.

 

This would mean, I could have a large application in one project and build different flavours of it's executable simply by using the appropriate build specs.

Use cases might include simple things like debug / release builds (similar to this idea), but also more complex differences like a software that uses real hardware and a special version that works without hardware, which can be used in the office.

 

Currently I need to either set the CDSs manually each time I build an executable or maintain several copies of the same project file. Both methods are tedious and error-prone.

 

Labels:
View All (3)
0 Kudos
christian_w

add COM compatibility to .NET Interop Assembly builds

Status: Duplicate Submitted by Active Participant on 12-08-2009 06:57 AM 3 Comment

I miss the possibility to 

 

- add COM compatibility to .NET Interop Assembly builds

- add COM  compatibility to Shared DLL builds

 

 

I missed LV help information about the need to add a key file (*.snk) to the project first, before you can select it for signing the assembly. Unless you do that the file filter (*.snk) seems to fail when browsing.

Labels: