Manifold WASM Developer Guide
    Preparing search index...

    Class CrossSectionGLTFNode

    Display a CrossSection in 3D space.

    A CrossSection object is two dimensional. Attaching it as a node allows it to be included in the final exported file, complete with transformations.

    Note

    CrossSections are not -- and can never be -- manifold. That means some exporters (like .3mf) will just skip over them entirely.

    Hierarchy (View Summary)

    Index

    Constructors

    constructor

    Properties

    crossSection? material? name? rotation? scale? translation?

    Accessors

    parent runID

    Methods

    clone isEmpty

    Constructors

    Properties

    crossSection?: CrossSection
    material?: GLTFMaterial
    name?: string
    rotation?: Vec3 | ((t: number) => Vec3)

    From the reference frame of the model being rotated, rotations are applied in z-y'-x" order. That is yaw first, then pitch and finally roll.

    From the global reference frame, a model will be rotated in x-y-z order. That is about the global X axis, then global Y axis, and finally global Z.

    This matches the behaviour of Manifold.rotate().

    scale?: Vec3 | ((t: number) => Vec3)
    translation?: Vec3 | ((t: number) => Vec3)

    Accessors

    • get runID(): number
      Internal

      Get the runID for this node. If there is no runID set, lazily assign one.

      We don't need these for regular operations, but they do help when converting to meshes for export.

      Returns number

    Methods

    Settings

    Member Visibility

    On This Page

    Constructors
    Properties
    Accessors
    Methods