LabVIEW Idea Exchange

There is a strange asymmetry in the conversion pallet:

I cant see any reason why it is not supported to use the type conversion on an array of FXP when it is on an element. It should be either none or both.

I'm totally on board with Embedding Labels for Property and Invoke Nodes! Here are some additional improvements to those nodes:

Property Node Concepts

Scripting and Invoke Node Concepts

1. Most importantly, the banner now more closely resembles a Static Control Reference.
2. The directionality arrows are a pixel width's larger - more distinct, and matching the size of the new LV2010 Local Variables.
3. The node banner is the same height as the unlinked property node.
4. Property Nodes and Invoke Nodes are distinguished by the Property Wrench and the Action Arrow glyph.
5. Scripting properties/methods are now more distinct. Currently, the small node banner inherits a few pixels of light blue distinction if any one property on the property stack IsAScriptingProperty. Proposed, shading will be applied on a per-property basis, allowing better visual distinction and a more coherent choice for what to shade.

Discussions/suggestions/insults/questions encouraged in comments section!

With the IPv4 address pool quickly getting used up I think we need to have native support for IPv6 connections in LabVIEW.

Right now a lot of SubVIs in Vision Development Module looks like that:

Because in most cases we using IMAQ Images on the top and error outputs - the wires fully misaligned. It would be nice if all (or most) of them will have standard and same "default" connector pane (if possible, of course).

Thank you!

Andrey.

It would be useful to be able to disable the handling of a single Event Case in an Event Handler Structure. Note that this is distinctly different from merely Diagram Disabling the contents of the Event Case; using that method, the Timeout event case will be reset, and additionally program execution will continue past the Event Handler Structure (in the example below, continue to the next iteration in the While Loop).

Here's an example of what a Disabled Event Case might look like - the Event Structure and contained code is "washed out" as if Diagram Disabled - additionally, the disabled event in the list of Event Cases is struck-out and in italics:

And here's a proposal for how one might disable a given Event Case, using the context menu that pops up by right-clicking the border of the Event Handler Structure:

When hovering over Typedef / Custom Control (*.ctl) in the Project Manager, the Context Help only shows the Icon and ev. a custom VI Description.

It would be very helpful if the Information and the wire pane image of the contained Control was also shown in the Context Help of the Typedef.

This improvement would reduce the needed effort to write VI Description or avoid opening several Typedefs until the right one is found.

Allow the user to right-click a given test result on the Results Window called "Retest", which re-runs the selected test, and if the test now passes where it previously failed, it clears it from the Results Window.

Start with this:

Right click on the selection, and select "Retest":

The VI Analyzer just retests the selected tests.  And then once complete, it returns to the VI Analyzer Results Window, with the selected tests cleared from the list (assuming they passed):

One of the fiddly things I seem to do more than I'd like is adjust the bottom of block diagram comments to the right height. At a minimum there, but also for similar text boxes on the front panel or subdiagram labels, etc. I'd like to have a snap feature that sizes to a multiple of the text height. Examples: