Skip to content

Update GeometryService.yaml #1145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 23, 2025
Merged

Update GeometryService.yaml #1145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 3 additions & 19 deletions content/en-us/reference/engine/classes/GeometryService.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,22 +26,6 @@ methods:
with their respective parents. Iterating over this table lets you decide
whether to reparent recommended constraints and attachments to their
respective parents.

Note that the `options` dictionary can contain the following:

- `tolerance` — The distance tolerance, in regards to `Class.Attachment`
preservation, between the attachment and the closest point on the
original part's surface versus the closest point on the resulting part's
surface. If the resulting distance following the solid modeling
operation is greater than this value, the `Class.Instance.Parent|Parent`
of attachments and their associated constraints will be `nil` in the
returned recommendation table.
- `weldConstraintPreserve` — A `Enum.WeldConstraintPreserve` enum value
describing how `Class.WeldConstraint|WeldConstraints` are preserved in
the resulting recommendation table.
- `dropAttachmentsWithoutConstraints` — Boolean with default of `true`. If
set to `false`, `Class.Attachment|Attachments` that have no
`Class.Constraint|Constraints` will be preserved.
code_samples:
- GeometryService-CalculateConstraintsToPreserve
parameters:
Expand Down Expand Up @@ -233,7 +217,7 @@ methods:
- When the `SplitApart` option is set to `true` (default), each distinct
body will be returned in its own `Class.PartOperation`.
- Each of the returned parts are in the coordinate space of the main
part. This means that the (0, 0, 0) of any returned part is
part. This means that the `(0, 0, 0)` of any returned part is
not necessarily at the center of its body.
- It's possible to call this method on the client, but with some
limitations. First, it currently must be done with objects **created**
Expand Down Expand Up @@ -366,7 +350,7 @@ methods:
- When the `SplitApart` option is set to `true` (default), each distinct
body will be returned in its own `Class.PartOperation`.
- Each of the returned parts are in the coordinate space of the main
part. This means that the (0, 0, 0) of any returned part is
part. This means that the `(0, 0, 0)` of any returned part is
not necessarily at the center of its body.
- It's possible to call this method on the client, but with some
limitations. First, it currently must be done with objects **created**
Expand Down Expand Up @@ -499,7 +483,7 @@ methods:
- When the `SplitApart` option is set to `true` (default), each distinct
body will be returned in its own `Class.PartOperation`.
- Each of the returned parts are in the coordinate space of the main
part. This means that the (0, 0, 0) of any returned part is
part. This means that the `(0, 0, 0)` of any returned part is
not necessarily at the center of its body.
- It's possible to call this method on the client, but with some
limitations. First, it currently must be done with objects **created**
Expand Down