Classes
Every enum and class in spinfireapi, organized by the package that defines it — mirroring the Class List in SpinFire Insight’s own scripting docs, rather than a flat alphabetical list.
spinfirescript
Class |
Values |
|---|---|
|
|
spinfireapi › assemblyitems
Class |
Values |
|---|---|
|
|
|
|
spinfireapi › sectionplanes
Class |
Values |
|---|---|
|
|
|
|
Sample - Calculate Cylindrical Radius
These two classes are defined locally in the sample script itself, not in spinfireapi.
Class |
Fields |
|---|---|
|
|
|
|
Referenced But Defined Outside This Package
These types appear as parameters or return values in spinfireapi function signatures but are defined in the underlying SpinFire.Scripting.API .NET layer, not in the Python source — e.g. StandardView (used by graphics.ApplyStandardView), CSPositionParams, CSOrientationParams, CSRotationParams (used by the coordinate-system functions in graphics.py), and various ...Data result objects (PhysicalPropertiesData, TreeItemsData, CoordinateSystemData, ProjectionAreaData, etc.) returned across several modules. The ones confirmed so far are listed in the next section.
Observed Return Types
These were recorded by running the Probe — Return Values script in SpinFire (embedded Python 3.9.2) with Filter.CATPart open. All the .NET types below are in the SpinFire.Scripting.API.Geometry namespace. Each object’s str() gives a readable summary. Coordinates print in the model’s units (mm for this model).
Function |
Returns |
Members |
Observed behaviour |
|---|---|---|---|
|
|
— |
The item name on success, e.g. |
|
|
|
Prints as a numbered list, e.g. |
|
|
|
Prints as parent and children, e.g. |
|
|
— |
Confirmation message. |
|
|
|
|
|
|
|
Same shape as |
|
|
— |
Confirmation message. |
|
|
— |
Switches on the YZ plane: every cut point it produced had X = 0, and the XY plane stayed off. |
|
|
|
Prints each cut edge as a list of points, e.g. |
|
|
|
If the requested plane is off, |
|
|
|
Prints as a list of points, e.g. |
Not yet known: the element types inside Items, CutPlaneEdges and Edge.Points; what AreaModel holds; and whether the Delete() method on LineData and ShellData behaves like DeleteLine/DeleteShell. It hasn’t been tried.