Click or drag to resize

Add Repeated Capability Dialog

For an introduction to IVI repeated capability topics, see the IVI Backgrounder topic entitled Repeated Capabilities.

Name

Specifies the repeated capability name. This name serves as a unique identifier for the repeated capability. The name chosen here is used registered by the driver installer in the IVI Configuration Store. In addition, the name chosen here is used as a base name for the following items:

  • I<driverName><repCapName> interface - the repeated capability interface on which the repeated capability methods and properties will be defined.

  • I<driverName><repCapName>s interface - (collection-style only) - collection interface on which the Count, Item, and Name properties will be defined.

  • repCapName>s property- (collection-style only) - reference property pointing to the repeated capability collection interface.

  • <driverName>repCapName> class - (collection-style only) - C++ class added to the driver source code for implementing the repeated capability methods and properties.

  • repCapName> property - (selector and parameter-style only) - reference property pointing to the repeated capability interface.

For example, if the name Channel is chosen for a collection-style repeated capability on a driver named Acme4321, then the following items would be created:

  • An IAcme4321Channel interface.

  • An IAcme4321Channels interface.

  • A property Channels that points to the IAcme4321Channels interface.

  • An IAcme4321Channels.Item property that returns an IAcme4321Channel interface.

  • An Acme4321Channel implementation class.

Style

The type of repeated capability to be added to the driver.

A discussion of the three types of IVI repeated capabilities can be found in the topic Repeated Capabilities.

Important note Important

IVI-C drivers do not support collection-style repeated capabilities. If the selected style is IVI-COM Collection, then the repeated capability will be treated as a parameter-style repeated capability when working with the IVI-C wrapper. This behavior is as per the IVI specifications.

See Also

Other Resources

Download a complete CHM version of this documentation here.