Save polymorphic VI as single file.

[xdaf]

Topic is discussed here.

If a polymorphic VI performs the same operation on 20 different data types, when browsing your user.lib (or other) palette, you'll have 21 different objects to choose from (unless you customize the palette). That's nonsense: only the main VI should be displayed.

Creating an LLB will solve the "single file" issue, but won't solve the confusion on the palette.

Customizing your palette can be a solution, but in case you're redistributing your VI/LLB, the user must customize it as well.

In the polymorphic VI window, the option "include source code" should be present: by doing so, main VI will become a container for polymorphic instances, and not only a link to them.

To edit polymorphic instances, user should double-click on correnspondent list item.

[Marc Blumentritt]

Two comments:

1.) If you save your sub VIs inside a folder starting with an underscore, it will not be displayed in your palette.

2.) What about executables? There is the option to remove unneeded instances of polymorphic VIs. In case of DAQmx VIs, this is a space saver. It would not work on a container file. Of course, making it a container is an option, therefore the user can choose himself.

[Dennis_Knutson]

It's also pretty trivial to distribute a palette. You just create the .mnu and include that.

[xdaf]

Hi Mark,

1) That's an useful suggestion: would you like please to post it on the linked thread? That should be useful for other user too (and so I can give kudos to your post).

2) EXEs are good for redistributing applications, my idea is intended for redistribution of source code to programmers.

[Darren]

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.