App GeoFeature

Introduction


An App GeoFeature object, or formally an, is the base class of most objects that will display geometrical elements in the 3D view because it includes a property.



Usage
The App GeoFeature is an internal object, so it cannot be created from the graphical interface. It is generally not meant to be used directly, rather it can be sub-classed to get a bare-bones object that only has a basic property to define its position in the 3D view.

Some of the most important derived objects are the following:
 * The Part Feature class, the parent of most objects with 2D and 3D topological shapes.
 * The Mesh Feature class, the parent of most objects made from meshes, not solids.
 * The Fem FemMeshObject class, the parent of finite element meshes created with the FEM Workbench.
 * The Path Feature class, the parent of paths created with the Path Workbench for use in CNC machining.
 * The App Part class, which defines Std Parts that can be used as containers of bodies to perform assemblies.

When creating this object in Python, instead of sub-classing, you should sub-class because the latter includes a default view provider, and  attributes for the object itself, and its view provider. See Scripting.

Properties App GeoFeature
See Property for all property types that scripted objects can have.

The App GeoFeature ( class) is derived from the basic App DocumentObject ( class) and inherits all its properties. In addition it has a property, which controls its position in the 3D view.

Properties App GeometryPython
See Property for all property types that scripted objects can have.

The App GeometryPython ( class) is derived from the basic App GeoFeature ( class) and inherits all its properties. It also has several additional properties.

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

Data

 * : a custom class associated with this object.
 * : the position of the object in the 3D view. The placement is defined by a point (vector), and a  (axis and angle). See Placement.
 * : the angle of rotation around the . By default, it is (zero degrees).
 * : the unit vector that defines the axis of rotation for the placement. Each component is a floating point value between and . If any value is above, the vector is normalized so that the magnitude of the vector is . By default, it is the positive Z axis,.
 * : a vector with the 3D coordinates of the base point. By default, it is the origin.
 * : the user editable name of this object, it is an arbitrary UTF8 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.
 * : a list of expressions. By default, it is empty.
 * : whether to display the object or not.

View

 * : a custom viewprovider class associated with this object.


 * : if it is, the object will show the bounding box in the 3D view.
 * : see the information in App FeaturePython.
 * : see the information in App FeaturePython.
 * : see the information in App FeaturePython.


 * : a tuple of three floating point RGB values to define the color of the faces in the 3D view; by default it is, which is displayed as  on base 255, a light gray.
 * : an App Material associated with this object. By default it is empty.
 * : an integer from to  that determines the level of transparency of the faces in the 3D view. A value of  indicates completely invisible faces; the faces are invisible but they can still be picked as long as  is.


 * : see the information in App FeaturePython.
 * : if it is, the object can be picked with the pointer in the 3D view. Otherwise, the object cannot be selected until this option is set to.
 * : see the information in App FeaturePython.

Scripting
FreeCAD Scripting Basics and scripted objects.

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

A GeoFeature is created with the method of the document. If you would like to create an object with a 2D or 3D topological shape, it may be better to create one of the sub-classes specialized for handling shapes, for example Part Feature or Part Part2DObject.

This basic doesn't have a default view provider, so no icon will be displayed in the Tree view, and no  properties will be available.

For Python subclassing you should create the object.