# Part

class `cee.usg.``Part`()

  A part describes the elements and nodes in one part of the `Geometry`.

  A part links a mesh defining the part geometry (mesh) with the settings for the part. Parts can share a mesh, and then e.g. use a transformation result to offset the parts.

  The part settings allows you to control the color, draw style, visibility and result settings for the part.

  A part can have a user defined name and a customData property is provided to store any application specific data for each part.

Accessors

- `customData`
- `mesh`
- `name`
- `settings`

## Accessors

`Part.``customData`()

  Custom data for the part. This field is not used by EnvisionWeb.

  Return type: | any

`Part.``customData`(data)

  Arguments: | data (`any`) – None
  Return type: | void

`Part.``mesh`()

  The mesh defining the elements and nodes of the part.

  Return type: | Mesh

`Part.``mesh`(mesh)

  Arguments: | mesh (`Mesh`) – None
  Return type: | void

`Part.``name`()

  The name of the part

  Return type: | string

`Part.``name`(name)

  Arguments: | name (`string`) – None
  Return type: | void

`Part.``settings`()

  Returns an active reference to the settings for this part.

  Return type: | PartSettings

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your multilingual generative AI assistant for documentation. Ask me anything about HOOPS Envision for Web in your own language, or choose a sample question below to start a conversation:

What is HOOPS Envision for Web?
What are the latest release notes for HOOPS Envision for Web?
How do I start evaluating HOOPS Envision for Web?
How do I write my first sample application?
How can I get assistance?

HOOPSY may store conversations according to OpenAI's policy. Responses may not always be accurate.

HOOPSY is thinking...