LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

I do not know if this is a new idea, but is so hard to add new fonts to LabView.  I think Labview should use the fonts stored in the computer instead of a fixed list of previously selected fonts on FP.

 

If we add a new font to the computer, this one should automatically appear on the list of fonts available to use.

 

FP

It would great if we could set the time of the CRIO controller via MAX as we select the time zone.....

When you hover (mouse) over a string control or indicator on the front panel of a VI, the tool automatically changes to the positioning tool when the cursor is over the border of the control or indicator.  Then, the tool automatically changes to the labeling tool when you hover over the interior portion of the control or indicator.  This behavior is perfect because you don't have to manually change tools to be able to enter or edit the text in the control or indicator.

 

I have noticed, however, that there is a different behavior for owned and free labels/captions on both the front panel and the block diagram as well as string constants on the block diagram.  If you hover over the border of these types of objects (both labels and string constants), the tool automatically changes to the positioning tool, as expected.  However, when you hover over the interior of these objects, the tool never changes to the labeling tool.

 

It would be really nice if labels and string constants behaved just the same as string controls and indicators on the front panel.  In other words, when hovering over the interior of labels and string constants, the tool should automatically change to the labeling tool.  You can currently access the text in labels and string constants by double-clicking on them, but it would be fewer mouse clicks if the tool automatically changed.  In addition, the behavior between free/owned labels/captions, string controls/indicators, and string constants would be consistent.

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.

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.

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

 

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

 

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

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.

 

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

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

 

 

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

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.

 

 

 

 

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.

 

sport the direction of array sort incresing or decsrising 

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,

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.

 

 

 

 

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 .

 

 

 

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.

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