Bitbybit Docs
    Preparing search index...

    Interface DesignBuildResult<T> (Models.OCCT)

    What design.build made: the parts, a report per feature (per component for an assembly) in document order, the problems found after the features ran (a part whose body failed, a property that could not be evaluated), the configuration used, the value of every parameter, and the structure that assembly.manager.buildAssemblyDocument turns into a document for STEP and glTF: each part once under the document, or an assembly's placements. An assembly adds its components, its joints and its bill of materials. units and up are the built document's, filled in where it leaves them out, for the exports and views that read them. pending lists the features whose outcomes the caller has still to make, such as scripts.

    interface DesignBuildResult<T> {
        parts: DesignBuiltPart<T>[];
        report: DesignFeatureReport[];
        issues: DesignIssue[];
        configuration?: string;
        parameters: Record<string, number | string>;
        components?: DesignBuiltComponent[];
        joints?: DesignBuiltJoint[];
        bom?: DesignBomLine[];
        structure?: AssemblyStructureDef<T>;
        properties?: Record<string, string | number | boolean>;
        units: Required<DesignUnits>;
        up: "y" | "z";
        pending?: DesignPendingScript<T>[];
        sketches?: DesignBuiltSketch<T>[];
    }

    Type Parameters

    • T
    Index

    Properties

    parts: DesignBuiltPart<T>[]
    issues: DesignIssue[]
    configuration?: string
    parameters: Record<string, number | string>
    components?: DesignBuiltComponent[]
    joints?: DesignBuiltJoint[]
    structure?: AssemblyStructureDef<T>
    properties?: Record<string, string | number | boolean>
    units: Required<DesignUnits>
    up: "y" | "z"
    pending?: DesignPendingScript<T>[]
    sketches?: DesignBuiltSketch<T>[]