LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Ther are 10 pages of suggestions coming up when typing "probe location on wire".

AFAIK, none of them addresses this irritating behavior of probes:

The probe icon will snap to some algorithmically determined location which might result in illegible data flow during debugging, or might end up in a region of the diagram far from where the critical action takes place.

I know that what matters should be the VALUE of the probe, but WHEN to check the probe value is also critical, and in a visual development environment, this time is determined by monitoring the data flow (among other methods). This is where this uncontrollable probe location can be annoying at times.

My suggestion: just as for labels, let the user choose the location of a probe anchor point on a wire (especially when it branches off).

View All (1)

The list of available LabVIEW modules and device drivers is very long. Their names tend to be long too, which is compounded by the many levels of nesting. Modern screens are large.

Given all that, why are we selecting software components by scrolling around a tiny window which can't be expanded?

(Note: most of the trees above aren't exen opened yet!)

Proposal: Make the window bigger (vertically and horizontally), or resizeable, or both.

Thanks for listening!

Problem Statement

Sometimes, you may want to delete files that are read-only. The Delete primitive outputs an error (Error 😎 when you try to delete a File that's set to read-only. One then has to change the file permissions to writable and retry deleting it. That's a pain. What's even more painful is when you try to delete a folder, recursively, with the Delete function -- passing it a folder path and setting Recursive to TRUE. In this case, if even a single file inside the folder is set to read-only, then the recursive delete will fail -- now, the developer has to do their own recursion to find the file that's read-only, mark it as writeable and then delete it. OK, convinced this is a pain? Here's the solution...

Proposed Solution

Add an input called "Ignore Read-Only" to the "Delete" function that will do all this form me.

Note

The OpenG Delete Recursive VI (in the OpenG File Library) has such a feature already. I was excited when LabVIEW implemented a recursive delete and I started using it all over the place (it's nice to write code that doesn't depend on external libraries, when possible) and then... I got bit by this limitation in some random corner cases where files had gotten marked as read-only.

Often when I want to look at the structure of a complex data type containing nested typedefs, I find the data type description in the Context Help quite heavy/verbose.

For example, could you tell at first glance how many levels of hierarchy there are in this data structure ?

Well, actually there are 5 levels (including the root cluster), but this is obfuscated by the unnecessary levels added by typedefs.

The description could be much more concise:

Here is an alternative that keeps the typedef type descriptions and appends them after the typedef name. However I'm not sure about this one because it could create description texts that are too long to be displayed in a single line:

Also for the configuration, it could be an option in "Options > Environment" and/or a button in the Context Help:

What are your thoughts ?

Raphaël.

View All (3)

This idea was posted years ago and declined for lack of interest (it got 6 out of 7 necessary, but I would have been the 7th!). I would like to bring it back, I would like my application to have access to it's own version number. In fact you can open the project programatically and see some build properties but not that one. I can then grab the version from the build properties and set the default values on my FPGA code before compiling.

I was trying to make a pre-build VI that would look at the build properties and copy the version data into a control. Can't be done. I find this very useful to make sure that my RT system and my FPGA code have the correct versions.

Same as with an about box, or version checking for compatibility.

The previous thread suggested a routine in the FileVersion.llb but that seems to only be available in a single platform. Not useful for RT linux or Mac. The version is not available until the executable is built which does not work for FPGA.

At the moment my only recourse is to hand copy the version from the build properties and then set those as a series of 4 integers on the FP. (Then select them all and set their values to default, hence the other suggestion about right click)

View All (1)

New tunnel mode: Build set

I searched but didn't see this idea yet. I'm surprised it hasn't already been suggested.

The idea is to add a "Build Set" to the Tunnel Mode menu:

Right now we have to build an array in the loop, then convert it with another loop. A native menu option, with the ability to keep the Conditional checkbox, would be very useful.

View All (2)

View All (5)

Even though I use the tools selection in the automatic mode, many times I need some specific tool not accessible in the automatic mode or force one like "Position/Size/Select". Sometimes, mostly designing User Interfaces (UI) that takes all screen, we got the Tools Palette blocking access to something. Then we move the Tools Palette until it get in front of something else.

The idea is to have an option to have all buttons in the toolbar. Some programs allows you "dock" just dragging the over the tool bar.

Many times we have plenty of space to have all buttons there, if not, we can have a second row of buttons. That will be nice to add more buttons as we wish.

PS: I added a swap button between the foreground and background colors. The idea is explained in this thread Swap Colors in Tools Palette.

View All (4)

Easier Reordering of Terminals

This is a follow on to this idea. After terminals are wired to growable nodes. Make it easier to move and reorder the terminals. The switcharoo tool exists if there are only two terminals but it is difficult if there are more.

I suggest making it easier with a keyboard/mouse combination or mouse long hold or something like that, to select a terminal. Then let the user drag it to another terminal and drop it. If that terminal is wired swap the selected wire and the one dropped over. If not wired, move the wire connection to the terminal dropped over.

View All (2)

View All (3)

Allow viewing of Map Constant as Icon

View All (2)

Quick Drop Replace Terminal

View All (1)

Color Picker Event On Mouse Movement

If I drop down a color picker control, I can get an event on it for when a new color is selected by using the value change event. But what if I want to know what color the user has their mouse over, before clicking on it? Many of NI's controls change color as you select a new color. The Graph plots for instance will update as you move the mouse around.

This idea is to allow color picking controls to have a new user event, which is Mouse Over Color which gets generated when the user mouses over a new color. This way we can make applications that change the color of some UI element before the user picks the new color like NI does.

This can be accomplished today by recreating the color picking functionality in a new VI. Here is one example posted that allows you to pick a color. Using this someone could generate a User Event, or post to a global as the new color selection is being made.

So the request here is to have an option wherein the array indicators (or controls) can be linked with another array indicator (or control) and can be scrolled synchronously.

There could be a property node for that (or invoke node or may be some other way), which will accept the reference of another array and thats all.

In above example, Array 1 is linked with Array 2, so whenever the user will scroll (or change the index of Array 2, the same change will reflect in Array 1.

View All (3)

Support Python Virtual Environments

View All (2)

LabVIEW Idea Exchange

Let the user choose the probe location on a wire

Improve readability of VI's membership in window title

Labelling wires can be made easy ..!! Take the control Name as default - Label Name for wire

Expand (or allow expansion of) NI software installer GUI

"Delete" (File) primitive should have an "Ignore Read-Only" input

Option for compact data type description in Context Help

Automatically updated version/build numbers: Exposing them programmatically for Help/About...menu item or Panel title

New tunnel mode: Build set

The default front panel Alignment Grid Size should be 10 pixels (instead of 12)

Add licensing and activation tools for packed project libraries (PPLs)

Option to dock the Tools Palette on the Toolbar

LabVIEW Find Search Scope - Add user.lib

Easier Reordering of Terminals

Disconnect Connector Pane Terminal with ALT + Left Click

Allow viewing of Map Constant as Icon

Quick Drop Replace Terminal

Color Picker Event On Mouse Movement

Allow to link two arrays so that they can scroll synchronously.

Support Python Virtual Environments

Simpler "Array Size"