LabVIEW Idea Exchange

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

I inherited lots of VIs with complicated terminal connectors. It is a challenge to determine which terminal is associated with a given control. 

 

Why not highlight the associated terminal when a front panel control has been selected?

 

In other words, currently when I select a terminal, the corresponding control is highlighted. I'm proposing that it should also work the other way -- when I select a control, the corresponding terminal gets highlighted. 

 

I have just figured out a workaround, but it's clumsy. I can temporarily delete the control, observe which terminal goes white, and then immediately restore it with Control Z. But my proposed solution would be cleaner. 

 

Thanks

 

Hi,

 

I suggest that radix is always visible when the numeric display format is other than decimal. Is this number decimal for instance?:

 

Number_188.png

 

Well, it was hex:

 

Number_x188.png  ... -> ...  Number_392.png

 

Basically you'd know that if there isn't a radix visible, then the number is decimal. It should still be possible to show radix for decimal numbers as well. This should be the case for both constants and controls/indicators.

 

Just one of those little things that would enforce a minimum of documentation.

 

Cheers,

Steen

It would be nice if the conditional tunnel would be polymorphic.  They only accept Boolean as condition.  Please add the error cluster, like it is available on Case Structure.

PolymorphConditionalTunnel.png

Array To Cluster Function, add Type to Convert Cluster

 

I rarely use this function, but when I do I always end up using Variant to Data function for my Cluster Type.

So I would like to add a Type terminal to convert cluster type.

 

111.png


If Type terminal is unwired, this function work as it in current version.

 

If it is wired then it will convert to cluster type, and further it can also be used to define cluster size. So this way we can adjust cluster size dynamically if cluster definition changed.

 

Thanks,

 

222.png

The idea is to know the result of the tunnel mode condition, in this case, it is to know if any element has been indexed.

 

whileconditional.png

 

This publication is motivated from the following discussion: Tunnel Mode Conditional .... output condition (by @ouadji)

 

Regards.

It would be useful if a special free label existed on the block diagram and/or front panel whose contents would be kept in sync with the contents of the VI description. For brevity, let's call this a Description-Linked or DL label. The screenshots below show an example.

 

1. The DL label shown on the block diagram

DL label 2.png

 

2. The DL label shown on the front panel.

DL label 1.png

 

3. The DL label shown in Context Help

DL label 3.png

 

4. A possible mechanism to show the DL label on the BD and/or the FP

DL label 4-edited.png

 

Suggestions

  • The DL label should have a distinctive background colour that cannot be changed (could be any pale colour)
  • It should be possible to show the DL label on both the BD and FP, only on the BD, only on the FP or neither in the BD nor the FP
  • Screenshot 4 shows a possible mechanism to show/hide the DL. There may be better mechanisms out there.
  • Selecting a DL label on the BD or FP and pressing DELETE (like when deleting a regular label) hides the DL label on the BD or FP respectively. Equivalent to unchecking one of the checkboxes in screenshot 4.
  • The two settings for showing/not showing the DL on the BD and FP should be stored within the VI. The settings should be preserved when creating a 'Save as...' copy of the VI.
  • It should be possible to independently resize and move the DL free label instance on the BD and/or FP (the size and position of the rectangle is not synced). Notice the size of the rectangle isn't the same in screenshots 1 and 2.
  • The DL label has no influence on whether other free labels exist in the BD or FP. Any number of free labels are still allowed.

This idea would ease the process of creating and maintaining well-documented code

  • When using a subVI inside a caller VI, the Context Help documentation is extremely useful (it may be the only documentation available if the subVI is part of a PPL)
  • When editing or inspecting a VI, the Context Help documentation is often not at hand. What is available at a glance is often a big free label comment somewhere on the BD or FP
  • As the VI is edited, the big comments on the BD and/or FP inevitably become out of sync with each other and with the Context Help
  • The DL label introduces the concept of having a 'master' documentation source, or a single source of truth
  • At Renishaw UK, some of us use an in-house scripting tool that searches for a free label containing the first word 'Description' on the front panel, and copies the remainder of the text into the VI Description. It's a useful workaround, but this idea would remove the need for such workarounds, and would add the benefit of two-way syncing (editing the VI Description to update the comments in the BD/FP).
  • drjdpowell suggested a similar idea (but not identical) in a comment to idea Subdiagram label for Block Diagrams too (screenshot below).

 

DL label 5.png

 

Thanks!

Hi.

 

I'd really like to be able to select the entire top-level cluster in an event structure, if event data is a cluster:

 

Top-level cluster.png

 

I know this have been brought up in numerous forums over the years, but I feel it's being ignored somewhat by NI? It usually gathers quite a few positive acknowledgements from other users, but I think it's about three years since it's been brought up in the idea exchange. It seems so easy to implement and would greatly simplify many event structures. So forgive me for duplicating something from countless other places, but I think it deserves a second (or ninth or whatever) glance Smiley Happy

 

Cheers,

Steen

Hello all,

 

It would be nice Smiley Wink to be able to drag a control or indicator from a block diagram, to a front panel or a "control editor" panel.  

 

DragAndDrop.png

 

For the moment you can only Smiley Sad drag "objects" ...

 

  • From a front panel to a front panel
  • From a block diagram to a block diagram

 

It would also be nice to be abble to drag ...

 

  • Constants from block diagram to front panels (Creating then a new control)
  • Constants from block diagram to "control editor" panel

 

Thanks.

 

Manu.net

When selecting properties from the Y Scale, I would expect to get the properties window opened for that axis.  But no, you get the properties for the x-axis.  But I distinctly selected the properties from within the Y Scale.  See image below.

 

My suggestion is to open the properties window to the axis where the selection was made from.

 

 

You can open a type definition by right-clicking a diagram terminal, constan, or front panel control, but it is not possible to get to a type def file just from a wire.  There are a lot of times where I'm working on a diagram that uses a type definition that is only exposed as a wire.  Right now, the process of getting to the type def is to create a temporary constant from the wire, then right click the constant.  It would be nice to make it easier to get to the type def.  And of course, I would like to have the same functionality for LabVIEW classes.

select.png

 

 

The issue is that there are some situation where we have multiple developers using the same PC (Ex. limited number of test stations where HW/SW integration is performed).  The last developer on the station changes the Environment Options to their desired settings.  

 

To allow a developer to quickly switch to their preferred set of Environment Options, we would like a feature that would allow the following from the LabVIEW Splash Screen: (see image suggestion below)

 

  1. Save current Environmental Option settings and assign that set a name.
  2. Export/Import to from system using a file.
  3. List the Environment Option sets currently on the system in the Tools menu
  4. Recall Environment Option set by name

 

Tools Menu.jpg

Well as the title says...

 

In the string constant you are able to make a scrollbar visible but this is still inconvenient when only see 2 lines of your whole string when you have a string constant of 50 lines or so... and you 9 out 10 times you don't want to create a bigger field because it messes with your diagram.

 

Therefore a small popup with a only a large textfield would grately simplify things.

 

I came up with this idea when I was writing a error message and there wasn't much space to type the string in, I also had this, http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Need-Edit-Window-for-New-Cluster-Constants/idi-p/1208295, idea in my backhead.

 

What do you guys think?

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.

Sometimes I want to insert a unconnected Sub VI on my panel into a some wire. I always end up deleting and reconnecting the wires to insert my Sub VI.

 

I miss a solution to quick insert a VI into a wire without deleting and reconnecting the wires.

example.jpg

I know we already have the option to use the QuickDrop with ctrl+I, but I miss a solution to insert a VI (that already exists on my panel) into a existing wire.

What about clicking on the wire and draging the Sub VI while pressing crtl+i?

It would save a lot of time if the Index Array function had options for Add Input and Remove Input. Currently when you need to add an input or to remove an item in the index array function you have to rewire the whole thing.

It would be nice if under options that highlight execution speed for debugging was configurable.  It could also be not an option but placed just next to the light bulb icon.  With experience we become able to folloe the code much faster and having 2 or 3 speeds of highlight execution could save some waiting time.  I know that there are many debugging options already but sometines the old light bulb is easiest.

 

Currently, the only native way to display a JPEG in memory on a 2D picture control in LabVIEW is to

  1. save to disk
  2. read from disk
  3. display

See: 

Screen Shot 2014-02-18 at 11.09.39 AM.png

This is not only silly, but slow: on a reasonable fast machine with an SSD, this takes almost a second!

A simple request: A VI that can go straight from JPEG binary data (other formats would be nice) to a 2D picture control. This is very useful for applications that download images from a server - a pretty common thing to do.

When doing UI work, it can be quite frustrating rewiring hidden controls to the connector pane. You have to go to the block diagram -> Show Control -> go to front panel and wire it up then hide your control again.

 

I have seen a number of ideas proposing ideas such as hidden controls always being visible in edit mode or being able to link block diagram controls to the connector pane which I agree with and would also solve this.

 

My suggestion is that when you select the Wiring Tool on the front panel or click on the connector pane (to wire up a terminal) all the hidden controls would become partially visible and become connectable to the connector pane.

1.png

 

a trueselect function, more powerfull Smiley Happy

 

 

d_a.png

When building an installer to let an application run on another computer one should select all the installers of products used in his porgram. This can be really tricky, especially to new users, that don't know if a VI was included in package A or B or if it's already included in the standrad runtime.

 

Therefore it should be possible to hit a button, that parses through the Application and determines which packages are used.

 

I though of writing something like this myself, but I can't be bothered Smiley Wink 

You'd just have to parse the Project, check all the VI names and relate it to a table that contains information, about where a VI comes from.

 

If this is a duplicate post, I'm sorry.