From ceb898650788a8ab6a0e442847fd5868ef0305b3 Mon Sep 17 00:00:00 2001 From: jdegenstein Date: Sun, 14 Jan 2024 16:52:09 -0600 Subject: [PATCH] key_concepts.rst -> Fix pending faces example e.g. change Fillet to fillet --- docs/key_concepts.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/key_concepts.rst b/docs/key_concepts.rst index f0583ed8..624e4d57 100644 --- a/docs/key_concepts.rst +++ b/docs/key_concepts.rst @@ -446,16 +446,18 @@ there was one. Here is an example: .. code-block:: python + height, width, thickness, f_rad = 60, 80, 20, 10 + with BuildPart() as pillow_block: with BuildSketch() as plan: Rectangle(width, height) - Fillet(*plan.vertices(), radius=fillet) - Extrude(thickness) + fillet(plan.vertices(), radius=f_rad) + extrude(amount=thickness) -``BuildSketch`` exits after the ``Fillet`` operation and when doing so it transfers +``BuildSketch`` exits after the ``fillet`` operation and when doing so it transfers the sketch to the ``pillow_block`` instance of ``BuildPart`` as the internal instance variable -``pending_faces``. This allows the ``Extrude`` operation to be immediately invoked as it -extrudes these pending faces into ``Solid`` objects. Likewise, ``Loft`` will take all of the +``pending_faces``. This allows the ``extrude`` operation to be immediately invoked as it +extrudes these pending faces into ``Solid`` objects. Likewise, ``loft`` would take all of the ``pending_faces`` and attempt to create a single ``Solid`` object from them. Normally the user will not need to interact directly with pending objects.