Std Part (Parte - Padrão)

From FreeCAD Documentation
Jump to navigation Jump to search
This page is a translated version of the page Std Part and the translation is 7% complete.
Other languages:
Deutsch • ‎English • ‎Türkçe • ‎español • ‎français • ‎italiano • ‎polski • ‎português do Brasil • ‎română • ‎русский • ‎한국어

Std Part.svg Std Part

Menu location
Default shortcut
Introduced in version
See also
Std Group, PartDesign Body


Std Part.svg Std Part (internally called App Part) is a general purpose container that keeps together a group of objects so that they can be moved together as a unit in the 3D view.

The Std Part element was developed to be the basic building block to create mechanical assemblies. In particular, it is meant to arrange objects that have a Part TopoShape, like Part Primitives, PartDesign Bodies, and other Part Features. The Std Part provides an Origin object with local X, Y, and Z axes, and standard planes, that can be used as reference to position the contained objects. In addition, Std Parts may be nested inside other Std Parts to create a big assembly from smaller sub-assemblies.

Although it is primarily intended for solid bodies, the Std Part can be used to manage any object that has a Placement property, so it can also contain Mesh Features, sketches, and other objects derived from the App GeoFeature class.

Do not confuse the PartDesign Body.svg PartDesign Body with the Std Part.svg Std Part. The first one is a specific object used in the Workbench PartDesign.svg PartDesign Workbench, intended to model a single contiguous solid by means of PartDesign Features. On the other hand, the Std Part is not used for modelling, just to arrange different objects in space, with the intention to create assemblies.

The Std Part.svg Std Part tool is not defined by a particular workbench, but by the base system, thus it is found in the structure toolbar that is available in all workbenches. To group objects arbitrarily without considering their position, use Std Group.svg Std Group; this object does not affect the placements of the elements that it contains, it is essentially just a folder that is used to keep the tree view organized.

Std Part-tree.pngStd Part example.png

Left: elements inside a Std Part in the tree view. Right: objects positioned in space, referred to the Origin of the Std Part.


  1. Press the Std Part.svg Std Part button. An empty Part is created and automatically becomes active.
  2. To add objects to a Part, select them in tree view, and then drag and drop them over the Part.
  3. To remove objects from a Part, drag them out of the Part, and onto the document label at the top of the tree view.


  • As of v0.19, a given object can only belong to a single Part.
  • Double-click the Part in the tree view or open the context menu (right-click) and select Toggle active part to activate or deactivate the Part. If another Part is active, it will be deactivated. See active status for more information.


  • At this time, Draft Snap methods do not work on selected Part containers nor on the objects inside of them.
  • A Part has no topological shape, therefore 3D operations like Part Boolean cannot be used on a Part itself. For example, you cannot select two Parts, and perform a Part Fuse or Part Cut with them.


A Std Part is internally called App Part (App::Part class), and is derived from an App GeoFeature (App::GeoFeature class), therefore it shares most of the latter's properties.

In addition to the properties described in App GeoFeature, the App Part class has some properties that help it manage information in the context of an assembly, for example, DadosType, DadosId, DadosLicense, DadosLicenseURL, DadosColor, and DadosGroup.

These are the properties available in the property editor. Hidden properties can be shown by using the Show all command in the context menu of the property editor.



  • DadosType (String): a description for this object. By default, it is an empty string "".
  • DadosId (String): an identification or part number for this object. By default, it is an empty string "".
  • DadosLicense (String): a field to specify the license for this object. By default, it is an empty string "".
  • DadosLicenseURL (String): a field to specify the web address to the license or contract for this object. By default, it is an empty string "".
  • DadosColor (Color): a tuple of four floating point RGBA values (r,g,b,a) to define the color of the object; by default it is (1.0, 1.0, 1.0, 1.0), which is displayed as [255,255,255] on base 255, white color.
  • DadosPlacement (Placement): the position of the object in the 3D view. The placement is defined by a Base point (vector), and a Rotation (axis and angle). See Placement.
    • DadosAngle: the angle of rotation around the DadosAxis. By default, it is (zero degrees).
    • DadosAxis: the unit vector that defines the axis of rotation for the placement. Each component is a floating point value between 0 and 1. If any value is above 1, the vector is normalized so that the magnitude of the vector is 1. By default, it is the positive Z axis, (0, 0, 1).
    • DadosPosition: a vector with the 3D coordinates of the base point. By default, it is the origin (0, 0, 0).
  • DadosLabel (String): the user editable name of this object, it is an arbitrary UTF8 string.
  • DadosGroup (LinkList): a list of referenced objects. By default, it is empty [].

Hidden properties Data

  • DadosMaterial (Map): map with material properties. By default, it is empty {}.
  • DadosMeta (Map): map with additional meta information. By default, it is empty {}.
  • DadosUid (UUID): the universally unique identifier (UUID) (128-bit number) of the object. This is assigned at creation time.
  • DadosLabel2 (String): a longer, user editable description of this object, it is an arbitrary UTF8 string that may include newlines. By default, it is an empty string "".
  • DadosExpression Engine (ExpressionEngine): a list of expressions. By default, it is empty [].
  • DadosVisibility (Bool): whether to display the object or not.
  • DadosOrigin (Link): the App Origin object that is the positional reference for all elements listed in DadosGroup.
  • Dados_ Group Touched (Bool): whether the group is touched or not.


The App Part only has the five properties of the basic App FeaturePython, and it does not have hidden properties.


  • VistaDisplay Mode (Enumeration): Group.
  • VistaOn Top When Selected (Enumeration): Disabled (default), Enabled, Object, Element.
  • VistaSelection Style (Enumeration): Shape (default), BoundBox. If the option is Shape, the entire shape (vertices, edges, and faces) will be highlighted in the 3D view; if it is BoundBox only the bounding box will be highlighted.
  • VistaShow In Tree (Bool): if it is true, the object appears in the tree view. Otherwise, it is set as invisible.
  • VistaVisibility (Bool): if it is true, the object appears in the 3D view; otherwise it is invisible. By default this property can be toggled on and off by pressing the Space bar in the keyboard.

Assembly concept

The Std Part is intended to be the basic building block to create assemblies. Unlike a PartDesign Body, an assembly is meant to be a collection of separate, distinguishable elements which are connected in some way in the physical world, for example, through pressure, screws, or glue.

Examples that could be Parts:

  • A wooden table that consists of individual wooden pieces (legs, top), which are put together by glue or metal screws.
  • A ball bearing that is composed of multiple steel balls, an inner ring, a retainer, a seal, and an outer ring.
  • An assembly of a screw with a washer, and a matching nut.

PartDesign Body contiguous separate.png PartDesign Body contiguous assembly.png

Left: three individual contiguous solids, each of them modelled by a PartDesign Body. Right: the individual Bodies put together inside a Std Part to create an assembly.

In general terms, when importing a STEP file into the program, the main assembly and its sub-assemblies will be imported as Part containers, each of them containing a simple Part Feature.

Detailed explanation

Active status

An open document can contain multiple Parts. An active Part will be displayed in the tree view with the background color specified by the Active container value in the preferences editor (by default, light blue). An active part will also be shown in bold text.

To activate or de-activate a Part:

  • Double click on it on the tree view, or
  • Open the context menu (right click) and select Toggle active part.


  • The active status of Parts was developed in v0.17 in parallel with the active status of PartDesign Bodies; however, as of v0.19 this status does not serve a real purpose for Parts.
  • Even when a Part is active, newly created objects are not placed inside of it automatically. In this case, simply drag these new objects, and drop them onto the desired Part.
  • Only a single Part can be active at a time.

Std Part active.png

Document with two Std Parts, of which the second one is active.


The Origin consists of the three standard axes (X, Y, Z) and three standard planes (XY, XZ and YZ). Sketches and other objects can be attached to these elements when creating them.

Part Origin tree.png Part Origin view.png

Left: Part Origin in the tree view. Right: representation of the Origin elements in the 3D view.

Note: the Origin is an App Origin object (App::Origin class), while the axes and planes are objects of type App::Line and App::Plane respectively. Each of these elements can be hidden and unhidden individually with the Space bar; this is useful to choose the correct reference when creating other objects.

Note 2: all elements inside the Part are referenced to the Part's Origin which means that the Part can be moved and rotated in reference to the global coordinate system without affecting the placement of the elements inside.

Visibility Management

The Part's visibility supersedes the visibility of any object it contains. If the Part is hidden, the objects it contains will be hidden as well, even if their individual VistaVisibility property is set to true. If the Part is visible, then each object's VistaVisibility determines whether the object is shown or not.

Part Visibility off.png Part Visibility on.png

The visibility of the Std Part determines whether the objects grouped under it are shown in the 3D view or not. Left: the Part is hidden, so none of the objects will be shown in the 3D view. Right: the Part is visible, so each object controls its own visibility.


A Std Part is formally an instance of the class App::Part, whose parent is the basic App GeoFeature (App::GeoFeature class), and is augmented with an Origin extension.

FreeCAD core objects.svg

Simplified diagram of the relationships between the core objects in the program. The App::Part class is a simple container that has a position in 3D space, and has an Origin to control the placement of the objects grouped under it.


See also: FreeCAD Scripting Basics, and scripted objects.

See Part Feature for the general information on adding objects to the document.

A Std Part (App Part) is created with the addObject() method of the document. Once a Part exists, other objects can be added to it with the addObject() or addObjects() methods of this Part.

import FreeCAD as App

doc = App.newDocument()
obj = App.ActiveDocument.addObject("App::Part", "Part")

bod1 = App.ActiveDocument.addObject("PartDesign::Body", "Body")
bod2 = App.ActiveDocument.addObject("Part::Box", "Box")

obj.addObjects([bod1, bod2])

You cannot create a scripted App::Part. However, you can add App::Part behaviour to a scripted Part::FeaturePython object by using the following code:

class MyGroup(object):
    def __init__(self, obj=None):
        self.Object = obj
        if obj:

    def __getstate__(self):

    def __setstate__(self, _state):

    def attach(self, obj):
        obj.Origin = FreeCAD.ActiveDocument.addObject('App::Origin', 'Origin')

    def onDocumentRestored(self, obj):
        self.Object = obj

class ViewProviderMyGroup(object):
    def __init__(self, vobj=None):
        if vobj:
            vobj.Proxy = self
            self.ViewObject = None

    def attach(self, vobj):
        self.ViewObject = vobj

    def __getstate__(self):
        return None

    def __setstate__(self, _state):
        return None

App.ActiveDocument.addObject('Part::FeaturePython', 'Group', group.MyGroup(), group.ViewProviderMyGroup(), True)