Grasshopper2.Componentsnamespace

Interface used for accessing input and output data from within Component.Process methods.

Script running as a component, rather than as a plain script.

Type of exception thrown when the access level for data in a parameter doesn't match with the predefined level.

Abstract class for all components.

Use this class to keep a record of the iterations a components sets up during solutions.

Implementation of IComponentParameters.

Assign this attribute to your component class if you do not want to allow optimised proxy construction. When a plugin loads all its components, it short-circuits the constructors to *not* add the input and output parameters, as this takes by far the most time. This however leaves the component instance in an invalid state. That usually doesn't matter because that particular instance is not used for anything, but if your component does require inputs and outputs to *always* be there, you must attach this attribute.

Base a script instance derives from. This is the type a scripter writes, and it does nothing on its own; each scripting platform provides its own implementation with the members a script is given.

Utility class for adding component input parameters.

Enumerates the possible meta data inheritance behaviour of component output parameters.

A utility class for creating a meta data mixing canvas.

An immutable collection of input/output metadata mixing relations using Parameter IDs.

Extension methods for mixing recipes.

A modular component makes it (relatively) easy to hide and reinstate any of the inputs or outputs. This is accomplished by maintaining a separate array of parameters which must have certain values in their CustomValues dictionary.

Utility class for adding component input parameters to ModularComponent instances.

An array of input or output parameters of a ModularComponent which maintains the hidden/shown states of the optional parameters.

Utility class for adding component output parameters for ModularComponent.

Enumerates the possible name/icon display modes components can be in.

Utility class for adding component output parameters.

Event arguments used in individual Parameter events.

Event arguments used in mass parameter events.

Lists the possible sides on which a parameter can exist.

Enumerates the possible processing levels for component solutions.