The PlugInSpecific property contains subproperties that vary depending on the plug-in. The PlugInSpecific property is an unstructured container, meaning the subproperties and subproperty data types can vary regardless of the NI_ModelPlugin type definition.

When you create a plug-in, the PluginSpecific property includes the following subproperties, each with a data type unique to the plug-in, as shown in parentheses. Edit the corresponding data type to add subproperties to each property.

• Options ( <plug-in name> Options)—Create subproperties to store any options or settings the plug-in provides. Typically, you implement the Model Plugin – Configure Standard Options entry point to provide a way for end users to edit the options you add.
• AdditionalOptions ( <plug-in name> AdditionalOptions)—Create subproperties only if you define a Model Plugin – Configure Additional Options entry point.
• RuntimeVariables ( <plug-in name> RuntimeVariables)—Use the RuntimeVariables subproperty to define variables the plug-in uses at run time. Create subproperties to share data within the same process model execution among the different entry points in the plug-in. The <plug-in name> RuntimeVariables data type must always include the following subproperty:
  • PerSocket (Array of <plug-in name> PerSocketRuntimeVariables)—At run time, the process model resizes the PerSocket array to include one element for each test socket in the system. By adding properties to the <plug-in name> PerSocketRuntimeVariables data type, you create per-socket variables you can use to share data within the same process model execution among the different entry points in the plug-in.

See Also

Thread-Safety of the PropertyObject API and TestStand Variables