Idea Exchange: Post your lonely orphans

[Broken_Arrow]

Do you have any lonely orphans in the Idea Exchange?   

If you have any Ideas that you think have been swallowed up in the void for one reason or another, post 'em here!

[Broken_Arrow]

To clarify: by saying "post 'em here" I meant to post links to the Idea, as opposed to posting the actual Idea here.

[Darin.K]

OK, I'll bite.  I have come to understand that I do many things to LabVIEW and in LabVIEW that others wouldn't, shouldn't or couldn't.  As such I expect my ideas to have limited appeal.  (I used to bug NI folks about recursion back in version 2, so I have an idea on the timescale involved as well).  That said, of all of my hare-brained ideas to have limited appeal, the only one that surprises me is this one:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Autowire-Property-Nodes-Created-From-Right-Click-Menu/...

When I right-click and Create Property For.. WTF am I going to do with that node besides go back and wire it to the terminal which I clicked on?  On top of that, when you are dealing with PNodes and INodes, you often have no choice but to have BDs which you need to scroll horizontally.  When the PN or IN is put on the cursor, you can't autoscroll like you can when dragging.

Here is my scenario.  Property Node near the right edge of my BD.  Right-Click, Create Method For..., scroll down to select method.  Now I have an Invoke node on my cursor.  Try to return to original spot but since the BD won't scroll I have to put it down, drag it to autoscroll, then go attach it to the original terminal.  aargh.

[Broken_Arrow]

Darin, that rocks. AND I haven't seen it. I guess Ideas are not "hot" unless they've had very recent Kudos. Anyway, Kudos!

[JB]

Help me save several minutes and hundreds of mouse clicks when configuring a new EXE.

[Broken_Arrow]

OK my turn:

I have never been satisfied with how Diagram Cleanup behaves in this respect...

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Diagram-Cleanup-should-not-move-loop-terminals-option/...

Perhaps too niche? I would love to have this...

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/A-Native-Function-to-Preallocate-Memory-in-a-Queue/idi...

[JB]

My turn again :

It should be easier to implement a splash screen.

[aeastet]

I have this one for the new icon constants that we get for cluster constants now. If you need to edit one it opens back up to full size. We need a window to edit in that does not cause the block diagram to grow.:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Need-Edit-Window-for-New-Cluster-Constants/idi-p/12082...

And this one for bulk adding to structures such as build array, concatinate string etc...

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Bulk-Add-to-array/idi-p/1187059

[tst]

This idea is hardly an orphan, but it has an actual shot of getting into 2011 with a few dozen votes.

Also, here are a few others which I feel really didn't get the love they deserved:

1. Show the default value of controls in subVIs which aren't required in the tip strip (will allow you to stop having to write the default value in the label, should have an effect on everyone)
2.  Add an easily accessible way to close an application (everybody needs to close their EXE at the end. This should happen automatically)
3.  Add "Add Element" and "Remove Element" to the Index Array context menu
4.  Adding a "(don't) wait until done" option to the Call By Reference node (a huge improvement if you run VIs dynamically using the Run VI method)
5.  Use the wiring tool to swap inputs or outputs which have been wired incorrectly
6.  Quick VI icon creation
7.  Add a "Concatenate Indexing" option for arrays leaving loops (relatively popular, but could still use a boost)

Here's a complete list of my ideas, for those who want to look through a few others.

[altenbach]

---

@tst wrote:

Also, here are a few others which I feel really didn't get the love they deserved:

---

Most of your numbered ideas in the post have invalid links...