# Part

class `cee.cug.``Part`()

Accessors

- `geometryIndex`
- `highlight`
- `id`
- `index`
- `name`
- `surfaceMesh`
- `visible`

## Accessors

`Part.``geometryIndex`()

  The index of the geometry in which the part belongs

  Return type: | number

`Part.``highlight`()

  Whether the part should be highlighted.

  Return type: | boolean

`Part.``highlight`(highlight)

  Arguments: | highlight (`boolean`) – None
  Return type: | void

`Part.``id`()

  The ID of the part within the given geometry

  Return type: | number

`Part.``index`()

  The index of the part within the given geometry

  See also geometryIndex

  Return type: | number

`Part.``name`()

  The name of the part

  Return type: | string

`Part.``surfaceMesh`()

  Show the element mesh on the surface of the part

  Return type: | boolean

`Part.``surfaceMesh`(mesh)

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

`Part.``visible`()

  The visibility of the part

  Return type: | boolean

`Part.``visible`(visible)

  Arguments: | visible (`boolean`) – None
  Return type: | void

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your Docs generative AI assistant. Ask me anything about HOOPS Envision for Web 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...