LabVIEW Idea Exchange

Make Nigel AI advisor able to analyze changes within git repo and suggest a commit message.

This would be useful to : 

• Make commit messages more relevant / use message conventions
• Avoid undesired changes
• Avoid undocumented changes

The Deployment Progress window should display the amount of time that has elapsed since the deployment started. The screenshot below shows a possible implementation.

Notes

• Please ignore the arrow that points at "Deployment completed with errors". I had to reuse this screenshot which was originally created to serve a different topic.
• This idea is similar to the following idea: The Build status window should display elapsed time. I created two separate ideas for the purpose of keeping each idea small and self-contained.

Feature or bug ?
Actually you can build polymorphic VIs with VIs with different pattern signature (the connectors block) and that's very nice !

But even if the Select type option let you choose every instance, only instances with the same signature can be selected others are ignored.
We should be able to select every VIs defined in the Polymorphic VI.

Hi,

When I use array constants on the block diagram I often expand them to show how many elements they contain - I even expand them one element further than their contents to leave no doubt that no elements are hiding below the lowest visible element:

Often it's not so important to know how many elements are in the arrays, nor even their values (one can always scroll through the array if one needs to know). But it can be very important to not get a false impression of a fewer number of elements than is actually present, for instance when auto-indexing a For-loop:

To be able to shrink array constants to a minimum size while still signalling that they contain more elements than currently visible, it would be nice with an indicator on the array constant when it's shrunk to hide elements (here shown with a tooltip that would appear if you hover on the "more elements" dots):

The information in the tooltip would be better placed in context help, but the important aspect of this idea is the "more elements" indicator itself.

Cheers,

Steen

Say you have new errors you want to merge into an existing structure. You have to expand the merge error, then bring the new error to the merge. Here is what I'm proposing.

Start wiring the new error, then click on the merge error node.

LabVIEW expands and connects the error wire

This would also be nice for any expandable node like build array, concatenate strings

Bonus points idea, but might cause more polarization so don't let the entire idea hinge on this. Clicking on an existing unbroken wire can insert the node.

The existing UI behavior just wires a new source into an existing wire, which really only breaks the wire. I'm not sure the above behavior would take capabilities away from the user. For build array to work this way, it would have to detect if the singleton was the same type as the array wire you were clicking on. This is a bit more iffy in my mind.

If you e.g. open a project in a newer LV and then close it; it starts recompiling everything with no abort option, and only after having recompiled 2000 VI's i can choose to _not_ save them ...

I just opened it to check a few things and ended up with Kill Process to get out of it.

Let us cancel/abort the recompile when shutting down.