polymorphic vis

[Labmaster James]

Hi,

I would like to create a polymorphic vi. I have read the help and it says I
should select File->new and then choose Polymorphic vi from the selection.
Unfortunately I cannot see a 'polymorphic vi' option. I have vi, control,
global variable, run-time menu, vi template, global variable template. There
is also an option 'start from template' and there no mention of
'polymorphic vi' here either.
I am using labview 6.02 on win nt 4.0 sp 4
So how do I do it?

Thanks

James

[Mike Manzheliy]

Hi,
see Contents and Index in Help menu (LabVIEW)

Complete the following steps to build a polymorphic VI.

1. Create two or more VIs with the same connector pane pattern. Make sure the
connector panes have corresponding input and output terminals
�if a terminal in the connector pane of one VI is an input, the corresponding
terminal on the connector pane of the other VI(s) also must be an input or it
must be unused. The same applies for output terminals. The VIs do not have to
have similar data types or similar subVIs and functions.
2. Select File�New to display the New dialog box.

3. Select the Create New radio button.
4. Select Polymorphic VI in the listbox and click the OK button to display the
Polymorphic VI dialog box.
5. Click the Add VI button to display the Choose the VI to open dialog box.
6. Select a VI to include in the polymorphic VI and click the Open button. The
VI appears at the top of the SubVIs list. This subVI determines the default
connector pane pattern for the polymorphic VI.

7. Repeat steps 5 and 6 to include other VIs. Any VIs that do not conform to the
default connector pane pattern appear with a broken icon. You can still save the
polymorphic VI. To change the order of the subVIs, select a subVI in the list
and click the up arrow or down arrow button.

Note Double-clicking a subVI in the SubVIs list opens the subVI.

8. Click the Edit Icon button to create an icon for the polymorphic VI.
9. Select File�Save to save the VI.

You also can remove a subVI from a polymorphic VI, edit the shortcut menu of a
polymorphic VI, and select the default instance of a polymorphic VI.

Hope it help you
Mike

James Annesley wrote:

> Hi,
>
> I would like to create a polymorphic vi. I have read the help and it says I
> should select File->new and then choose Polymorphic vi from the selection.
> Unfortunately I cannot see a 'polymorphic vi' option. I have vi, control,
> global variable, run-time menu, vi template, global variable template. There
> is also an option 'start from template' and there no mention of
> 'polymorphic vi' here either.
> I am using labview 6.02 on win nt 4.0 sp 4
> So how do I do it?
>
> Thanks
>
> James

[CraigGraham]

You didn't mention what I suspect is the fundamental problem here; you need
the Professional Development System, the most expensive one, to be able to
do this.

Mike Manzheliy wrote in message
news:3AC46663.E6EF5907@levsha.ru...
> Hi,
> see Contents and Index in Help menu (LabVIEW)

[Labmaster James]

Typical.

"Craig Graham" wrote in message
news:3ac46b65@newsgroups.ni.com...
> You didn't mention what I suspect is the fundamental problem here; you
need
> the Professional Development System, the most expensive one, to be able to
> do this.
>
> Mike Manzheliy wrote in message
> news:3AC46663.E6EF5907@levsha.ru...
> > Hi,
> > see Contents and Index in Help menu (LabVIEW)
>
>
>

[CraigGraham]

I also found it irritating, having been looking forward to it since it was
announced. Our "Full Development System" obviously uses a curious definition
of the word "Full"- I expected there to be additional toolkits supplied with
the PDC but not core functionality.

However, you can often achieve a similar end result by using "variant"
datatypes; whatever you wire to them is coerced on the fly to a variant, and
you can then cast the variant back to various datatypes in the sub-VI.

James Annesley wrote in message
news:3ac488c1@newsgroups.ni.com...
> Typical.
>

[stop bugging me]

For some reason NI has choosen to cripple LV _Full_ Developement System hence you will have to pay for the Proffesional Developement System to get this functionality. One can compare it with shipping a C-compiler with out support for the "void" type.

Cheers,
//Anders