Option to add malleable VIs directly into project

[_carl]

I tend to use malleable VIs more often than half of the items in the "New" context menu list when you right-click within a project, however, it's not an option:

Instead, I either need to:

- Create a new VI and then make several property modifications, and save it as a ".vim".

- Create it through the file menu and then remember that I need to move it to the appropriate place in my project, because it gets created at the top-level.

Why not include this in the context menu?  (Bonus points if Polymorphic VIs get added too!)

[JÞB]

Expand the Idea to "Add>> New..." to get New vi from Template,  New lvlib, New Global.vi ad nauseam.

In fact, I've been pitching that for years! And it's a decade overdue.

In practice,  the existing Framework Provider tools are available to roll your own tool to add the functionality yourself but, then you have to deploy the TK to your developer team. 

That really blows when you are consulting so, I hide the fact that my machine has the capability and often need to excuse my language when assisting a client.  Then, of course, there is Language Support that I will NOT provide. 

---

[wiebe@CARYA]

>Framework Provider

Better known as the Provider Framework or, more complete, the Project Provider Framework. 😉

[AristosQueue (NI)]

JÞB, the idea to do that with global VIs was explicitly shot down as making globals too accessible (high barrier to globals considered good discouragement). I remember that conversation. I wasn't part of the convo for the other items in New, but my guess is that they were seen as low frequency of use and not worth clouding the very high traffic New pull right.

Weirdly, I don't recall it ever coming up for malleable VIs.

[JÞB]

I really don't care if you pull out the Global.vi from the Dialog launched with Menu selection "File>>New..." and not to be confused with File>>New hotkey Ctrl + N.

I just want the New... dialog to launch and place the New... File in my lvproj in the right location. 

AFAIK 7th floor at Mopac should offer a bonus check to the developer that sneaks in and tosses Global.vi out from the templates folder.  While you are at it, save all of us developers a bunch of time and FORCE us to use New... rather than always starting with a blank.vi.

Generally speaking,  I usually have some concept in mind clearer than blank when I want to create a vi and New... lets me create a blank.vi if I do want one.