LabVIEW Idea Exchange

Tunnels for FOR loops are autoindexing by default. Sometimes this is not the correct option for very obvious reasons and we get a broken wire.

The diagram editor should be smart enough to try the "other" option (e.g. no autoidexing) if a broken wire results. If the other option succeeds without a broken wire, it should be used automatically. Maybe the tunnel could "glow" for a few seconds with a small option box (similar to e.g. when pasting into word: keep formatting, text only, etc) that would disappear after a while where we can click and overwrite the automatic handling.

The image shows two wires that would be a candidates for autocorrection of the indexing option. In both cases, LabVIEW should disable indexing automatically to avoid broken wires.

If both options result in a broken wire, nothing should happen, as before.

(Similarly for while loops. e.g. if I wire a scalar across the boundary to an array indicator, it should autoindex.)

I use Splitter extensively to create resizable GUIs. However, if I create my resizable GUI and then my customer asks me to add parameters in a new pane on the left, I can't add to an existing GUI a splitter in the top of the hierarchy, i.e. a new vertical splitter that all the existing splitters will be on the right of the splitter and a new empty pane on the left. Any splitter I add will be added to the bottom of the existing hierarchy, and there is no way to change this. So to do this I basically need to rebuild the GUI again from scratch.

Another example, if this is my GUI:

I can't add a status bar now, as any horizontal splitter I add will be inside an existing pane, and this can't be modified. However, if this idea were implemented, I could View splitter hierarchy and create a new horizontal splitter at the top of the hierarchy so that I would have my status bar without rewriting the whole thing.

Thanks,

Danielle

Problem: my code accesses many different properties of many different controls. I need to locate where a specific property of a particular control is read/changed.

I know that the Find panel offersi me the option of searching by text, like

but that is not the solution, because I need to type thename of the property, and because I may match many other objects with the same string (comments, other controls with the same property, etc.)

I'd like a faster way to get to where I need. For instance the contetual menu could offer Find/specific property according to where the right-click was.

instead of using the right-click context menu / using ctrl+H and then selecting help,

use F1 to go to the topic

LabVIEW is awesome. But sometimes things don't go quite right, and when something isn't quite right somewhere (maybe a bad bit of binary) it would be great to be able to recompile your code. Mass Compile is great for upcompiling from older major versions, but will ignore VIs that are already compiled in the current version. What I'd like to see is a "Force Recompile" flag in Mass Compile to ensure all identified VIs are most definitely recompiled, especially useful when you call Mass Compile from the shortcut menu in Project view.

Yes, it could take some time, but less time than scripting it and you can use the time to make yourself a nice cup of hot British tea.

I love the new integrated structure labels! I will probably be using the free text labels much less in LabVIEW 2012. But they need a vertical scrollbar and probably a horizontal scrollbar as well. We can debate about whether or not it is a good idea to have hidden text in the labels. But regardless there needs to be some indication if there is.

This is closely related to another idea here.