LabVIEW Idea Exchange

Hi to document my VI BD I use more and more the Wire Label. 

When we Make it visible:

The beginig of the entry is centred to the wire:

But one problem with it is when we type text, the text is Left Justify:

So I propose that the default alignment for the text should be Center Justify:

Thank you

I wonder whether it has been posted before.

When creating an Indicator out of Index array, Replace Array subset and Insert into array the indicator are not inline with the output terminal. We cannot call that as a bug, I propose it here so that it may be corrected in future.

There is something wrong with this VI, although you wouldn't know it unless you ran it (and I should warn you that it will annoy you if you run it):

What's wrong with it is that auto grow has been disabled and there's some annoying code hidden there beyond the loop boundary. This is one of my least favorite things about LV - it allows us to hide code completely and get away with it. I don't think it should.

LV already has auto grow enabled by default to handle some of the cases which cause this issue, but I know that many many people don't like it when LV automatically plays with their BD layout (and rightly so) and auto grow only covers some of the cases, so I think we need something more encompassing and less obtrusive, and I would suggest breaking the VI if it has hidden code.

I also know that LV has warnings and VI Analyzer has tests for this, but I think this needs to be something which doesn't let you get away with it.

I think LV should break any VI which has any of the following:

• Objects beyond the visible boundaries of structures (including wires and constants).
• Objects behind other objects (possibly not including wires).
• Overlapping tunnels on structures (or maybe just not allow them to overlap at all)?
• Anything else?

It's great that you've put connector pane and VI icon side by side in the Front Panel

It's more useful if you can put the same in the Block Diagram

Howdy!

It would be really cool if I could drag and drop a polymorphic VI from its icon on the the block diagram of a VI, just like a standard VI would do it. The other ways include via the LabVIEW Project or from disk, but I would find this new method quicker when I already have the Polymorphic VI open.

Whilst I am at it, some other things that could be supported include better context help - I get this when really I want the description of the Polymorphic VI to show:

Cheers

-JG

PROBLEM:  There are often times when I decide I would like to include some code that is just outside of a structure.  Currently in order to get it into the structure I have two options:

1. Grow the structure, move the code inside, reattach all the wires, rearrange code so that the spacing is correct again.
2. Delete the structure and readd it.  (This option is not valid for sequence structures where I'just want to move code from one frame to the next.)

SOLUTION:  Allow a control (or shift) when resizing a structure that causes the structure to capture the code rather than move it.  This should not break any wires.  In essence, it would be like redropping the structure..  Note this could also work in reverse.  If you size a control smaller, it would exclude anything outside the new boundaries of the structure.