LabVIEW Idea Exchange

"Auto-insert Feedback Nodes in cycles" option under Tools > Options > Block Diagram should default to OFF. I am a believer and preacher of FN's since Darren's blog post about them, but it seems I can only get FN's to appear when I mis-wire, not when I want one.

Plus, they really scare LV beginners (and me!) when I miswire. GAH! What just happened??

Each page of a tab control should behave just like a pane does.

This means it should be possible to put splitter bars on a tab page.

This way one could build real nice front panels that look good when resizing, even when using tab controls.

At the moment I always have to decide: Do I need several tabs or is it important to be able to resize the panel?

There is no way to have both at the same time

(OK, there is one way - but I know much better ways to spend my time than programming all those pixel calculations to resize every control programmatically  )

Here is a quick scetch of a dialog front panel that could be improved very much by using splitter bars and  "fit control to pane":

Look what happens when the panel is resized: It's a big waste of space that could be put to a better use by extending the tree.

I did a search for explain error - I did find this idea which is similar but for probes.

Explain Error is a feature I have been using more lately but its not available for an error that is in an array (LabVIEW 2010).

It would be great if it was!

Cheers

-JG

When do I use the Run Continuously button?

Almost Never. And most times I hit it, it's an accident and it's a pain.

PLEASE hide it by default on all new VIs.

Structures have many right-click options, but the property dialogs are currently very sparse (only label and subdiagram label). Let's compare the current right-click options of a FOR loop with the actual properties dialog, and we can see that many useful properties are missing (visibility of conditional terminal, autogrow setting, etc.). The parallelization has it's own standalone dialog, why not have all these settings on a new tab instead?

I propose that these scattered properties should all be integrated into the single properties dialog to keep things better organized. Here's how the properties dialog of a FOR loop could look like after implementation of this idea.

Similar changes could be made for all other structures.

LabVIEW's case selector icon (?) is taller than tunnels, so it interrupts wiring flow whenever a standard VI (4-2-2-4 terminal configuration) uses one of the terminals as the selector and an adjacent terminal is also wired as a tunnel.  I'd like to see the case selector be the same height as a tunnel.

Hi.

I suggest an ellipsis be added to long enum or text ring values if they don't fit in the control. As it is today long values are line-breaked at last fitting hyphen (for instance):

 -->

Instead I'd like as much text as possible to be displayed with an ellipsis at the end. The above example would then become:

Cheers,

Steen

Oftentimes, I'll use a probe simply to see if code has executed, waiting for the probe value to change from "Not Executed" to the value on the wire once it's first executed. Having a "Reinitialize" or "Reset to 'Not Executed' " context menu item would make debugging iterations faster.

Make the Panel Resize event in the event structure a filter event.  This would allow for clean, professional looking control of VI panel size.  Use cases include: limiting the maximum panel size, preventing a panel from resizing in one direction, only allowing the panel to resize in discrete increments, etc.

In traditional windows programming, filtering the WM_RESIZE event is often used to control window size and I'd like to see this same functionality come to LabVIEW.

Ideally, this change would include a Discard? option as well as NewBnds and Act as options in the Event Filter Node.  Setting NewBnds or Act would allow the programmer to amend the resize before it takes effect.

Originally discussed here, this would be a time saver in quite a  few cases:

when dropping a structure (sequence, case, while or for loop, etc) over wires, an option should be provided allowing these wires to go through the structure (instead of ending up untouched UNDER the structure as is currently the case). Maybe with a modifier key?

Illustration:

Starting from this simple situation, where I want to do some comparison on the two strings (please imagine that the wires go through a lot of hooplahoops rather than directly to the indicators shown, as otherwise the solution is trivial):

I currently need to drop a sequence structure and do all the connection manually before creating a subVI (or doing stuff in a case structure, see below):

The suggestion is to go directly to this:

The reasons this would be useful are plenty, I think.

For instance, you want to do some sanity check on a bunch of wires now that you have added a new control on your panel. As of today, you need to drop a case structure, get wires you are interested in one at a time, connect them to the left of the structure, pass through the structure, connect them to the right of the structure, delete the wire underneath the structure, reconnect them to the right tunnels, etc...

Now, for a case structure, there might be some options on how to do that (for instance connect the wires through all cases? through the True case only?). Likewise for a while/for loop (you could autoindex at the entrance and/or at the exit, a mess that already exists anyhow).

My 2 cts.