Home Community Idea Exchange LabVIEW 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
0 Kudos
DJed

Control-B "Remove broken wires" should work on conditional disable structures

Status: Declined Submitted by on 11-12-2010 10:30 AM 2 Comment

I know that code that is disabled cannot be properly cleaned and processed by labview but it would be nice it control-b at least removed loose ends on wires in the disabled structures.

Labels:
0 Kudos
DJed

Wires should be part of the z-plane order

Status: Declined Submitted by on 11-12-2010 10:21 AM 4 Comment

Wires are not part of the z-plane ordering and so you cannot put things behind wires.  "Send to back" and "Send to front" aren't options when you click on a wire.

Labels:
0 Kudos
Edbarrow

Better timing structures

Status: Duplicate Submitted by Member on 11-10-2010 09:51 AM 3 Comment

In many of my programs, it is frequent that I have to issue a command, then wait for a period of time before reading a response. Usually, if there is a timing delay in code, it is usual to end up with something like this:

 

timing2.png

 

To do this more neatly, I created a timing subVI with errors wired in and out, and a number wired to it, to instruct the program to stay in that subVI for that period of time. It takes up much less space.

 

timing3.png

 

By doing this, I can easily control timing and execution. However, it's be nice to rework the 'milliseconds to wait' diagram so we could wire errors through it, as this would make the block diagrams so much neater...

 

0 Kudos
Dave_RS

Re-use of a selection of VIs within an LLB or project

Status: Declined Submitted by Member on 11-03-2010 05:08 AM 1 Comment

It would be useful to be able to create a new project containing just a selection of VIs, without having to either:

1. Copy all of the VIs and just use the ones that are necessary - this is very wasteful of disk space

2. Manually go through the hierarchy view looking for and noting the names of the VIs, globals etc and then copying them into a new project area - this is very costly as it takes a long time.

 

It would be great to be able to select a VI to clone, show the hierarchy and then say right click on the top level VI and have the option to CREATE A NEW PROJECT BASED ON THIS HIERARCHY. Even better would be the additional option to deselect any VIs that you know are not needed, before creating the new project

 

Labels:
0 Kudos
nidhi_ug

Multiple Variables/Controls of the same name

Status: Duplicate Submitted by Member on 11-01-2010 06:43 AM 3 Comment

If i am creating a new control of the same type as the first one, for the second time, the name automatically changes by concatinating "space 1 ". that is fine. but simultaneously i have option of having the same name as the first control by editing.  When i am creating variable it is confusing for which control i must relate it to untill unless i find the control and check.

 

I want to know (some kind of information on availability of the same name for another control) while editing the variable name of the same type is available.

 

Should it be allowed?

 

needs some clarification on this..

Labels:
0 Kudos
ChristopheC

A data entry parameter to specify if an integer can only be odd or even.

Status: Declined Submitted by Active Participant on 10-29-2010 01:50 PM 8 Comment

It is not uncommon to have to restrict numeric entries to accept only either odd or even values. It would be nice to be able to specify that behavior, for example in the Data Entry tab of the Properties dialog, so we don't have to write some code to enforce that restriction, with the Response to value outside limits to either round up or down. This would apply to integers only.

 

Labels:
0 Kudos
Kikujiro

Focus Color

Status: Duplicate Submitted by Member on 10-25-2010 07:57 AM 3 Comment

To improve the quality of interfaces, we need to change the color of the focus rectangle. Otherwise we do not see anything on a dark interface.

Download All
Labels:
View All (1)
0 Kudos
Spectre_Dave

Offset Shift Registers

Status: Declined Submitted by Active Participant on 10-22-2010 09:04 AM 6 Comment

I do a fair amount of Pipelining and it would be cool if I could Offset the Input Shift Register from the Output Shift Register.

The default would be to keep them aligned but a right - click would give me the option to offset the input or output Terminal. I think it would be bad form to allow crossing the terminals between multiple Shift Registers so the top Input terminal would correspond to the top Output terminal.Offset Shift registers.JPG

 

 

Labels:
View All (2)
0 Kudos
Hassan_Atassi

LabVIEW version identification in windows task bar

Status: Duplicate Submitted by Active Participant on 10-15-2010 04:19 PM 3 Comment

If you have multiple version of LabVIEW opened, it is difficult to tell which version is which by looking an the windows task bar.  There should be some differentiation between versions for easy identification.

 

 

Product_suggest.JPG

Labels:
0 Kudos
safar

multipage tiff format

Status: Duplicate Submitted by Member on 10-07-2010 11:13 AM 2 Comment

i like that the function write image en tiff format sport a multipage imagen.so the read image sport to read the selected image numeber from tiff format.

 

 

Labels:
View All (1)
0 Kudos
JÞB

Resettable Queue Max Elements

Status: Declined Submitted by Knight of NI on 10-06-2010 07:28 PM 9 Comment

 

 

I Hit on a post today that required a Queue function "work-a-round"

 

The Poster simply wanted to reset the property "Queue.MaxLen" and that property is quite buried.  (and look at the bug in probes on queues where "number of elements in queue" must = "0").

 

One solution was: ReSizeQue.png

 

A better (IMHO) solution would be to drop the "set" method of "Get Queue information" function on the BD and solve the problem with a single call of a vi.lib object.

 

Labels:
0 Kudos
safar

array sort

Status: Duplicate Submitted by Member on 09-28-2010 06:11 AM 7 Comment

sport the direction of array sort incresing or decsrising 

Labels:
0 Kudos
safar

Imagen multipaginas

Status: Duplicate Submitted by Member on 09-28-2010 04:16 AM 2 Comment

arLos imagines de formato tiff permite guardar varios imagines en LabVIEW no tenemos posibilidad de guardar  varios imagines en el mismo fichero tif ni leer los siguientes solo lee el primer imagen que encuentra en fichero,

quiero posibilidad de guardar y leer varios imagines en el mismo fichero tiff o cualquier formato estandar que permite varios imagines en el mismo fichero por ejemplo DCX,

Labels:
0 Kudos
M_Peeker

Selected VIs search from virtual folder

Status: Declined Submitted by Member on 09-24-2010 03:54 AM 1 Comment

If I press ctrl+f while the root project is highlighted I get the "Find Project Items" window. This is all well.

 

However, if i press ctrl+f on a folder in the project, the "Find Project Window" is also opened, with the same search scope as when the root project is highlighted. To me this is not the expected behaviour. There are two other things that would be more relevant:

1. Perform an project items search (recursive) within that virtual folder.

2. Perform a Find operation such as the one we get when we press ctrl+f on a BD or FP, with the search scope set to "Selected VIs" and with the VIs in the virtual folder (recursively) set as "Selected VIs to Search".

 

My suggestion is case 2, perform a selected VIs seach directly from the virtual folder.

 

 

 

 

Labels:
View All (4)
0 Kudos
Rafa L

Making zoom to a Block Diagram

Status: Duplicate Submitted by Member on 09-22-2010 04:47 PM 1 Comment

24520iD10181C16C0EBC8E Many

 

Many developers have to program on laptops that usually come with a limited screen. How if in Labview, we could use a zoom capability on block diagram. It could works fine also using the mouse scroll. Very usefull to little screens .

 

 

 

Labels:
View All (4)
0 Kudos
WiMAX_Eng

Disable Parts of the Block Diagram

Status: Declined Submitted by Member on 09-21-2010 05:02 AM 12 Comment

I don't think this has been discussed before but apologies if it has...

 

Similar to the 'skip' feature of a step in TestStand (or comments in text based programming languages) it would be nice to be able to disable parts of the block diagram to bypass parts of the code.  I do this often in electronic simulation packages to bypass (route around) parts of a circuit which can be helpful in design or debugging by isolating areas or switching off functionality.  In this way you don't have to delete anything to bypass it.  To show which parts are disabled in the block diagram those parts would be greyed out or ghost.  This of course may also affect controls and indicators which should similiarly be ghost (which has already been suggested to signify hidden controls/indicators).

I guess the alternative is to use case statements with false constants but this can mean creating space and making a mess.

Labels:
0 Kudos
P@Anand

Disable the functionality of the function keys (F1, F2...) while code is running!!!

Status: Declined Submitted by Trusted Enthusiast on 09-20-2010 09:19 AM 6 Comment

Its better to disable the functionality of the function keys while a code is running.

 

One incident i came accross is:

     I assigned ESC key for a control and while running the code i wrongly pressed F1 (Which is not assigned to any control) suddenly the Help file started opening and my whole code got hangged. I dont think that some one will need open the help file during code running So its better to disable the original functionality of the function keys just during the code is running.

 

Smiley Wink

0 Kudos
rgvandewalker

Right clicking can find and change any attribute.

Status: Declined Submitted by Member on 09-17-2010 02:02 PM 4 Comment

I'm a first-time user of labview, but a very experienced programmer in other languages. 

It was impossible for me to find a complete, modifiable list of the changeable properties associated

with an icon on the block diagram.

I kept expecting this to be available when I right-clicked the middle of an icon in the block diagram, or a control on the control panel.  At first I expected to be able to right click connection nodes and get connection properties, as well.

The expectation was initially almost unconscious, so I believe it is deeply ingrained, and might be common in other users.

This is the predominant mode of interaction in MS Windows applications, and I think it can be convenient in other UIs.

If so, Labview would be more intuitive if it leveraged this preexisting user training.

 

Labels:
0 Kudos
P@Anand

Controls get displaced while ctrl+click drag

Status: Declined Submitted by Trusted Enthusiast on 09-17-2010 01:29 AM 3 Comment

I found this behaviour of LabVIEW some months before and till now i didn't get the answer that why am posting here.

 

When i have some controls in the front panel if i press ctrl key and left mouse button and drag between the controls it gets displaced. Is that a short cut key for aligning the items? or does it has any functional use?... I am really puzzled with that behaviour and no body knows the answer (the person i met) for it. If it is a strange behaviour and do not have any proper use then in the next version the architects and champs of LabVIEW can try removing the behaviour.

 

Smiley Wink

 

 

Download All
Labels:
0 Kudos
Mads

Projects should be able to ignore that a file is a VI or .llb

Status: Declined Submitted by Active Participant on 09-16-2010 06:45 AM 9 Comment

I often need to build applications and installers that include VIs or .LLBs that have been built  earlier on...but this is a major pain because as long as LabVIEW recognises the file type it will try to link the VI or VIs in the library to the other VIs in the project, it finds conflicts etc. There are ways to come around it yes, but not very elegant ones.

 

Basically what I want is for projects to be able to treat VIs and LLB files as non-LabVIEW files. Just like you can include a text file, a JPG picture or other files in your project and installers I want it to be simple to add "completed" LabVIEW files.

 

One solution could be to have another type of project folder. We have auto-populating folders...perhaps we could have a folder for pre-compiled / to be treated as external sources folder...? In most cases for me LabVIEW could just see that the file does not contain any source code and then treat it as a "dead" file..or at least give you the option to do so (if there is a potential conflict).