FBGeometryMappingMode Class Reference

#include <mobu-python-api.h>

Class Description

Determine how the element is mapped on a surface.

• kFBGeometryMapping_NONE The mapping is undetermined.
• kFBGeometryMapping_BY_CONTROL_POINT There will be one mapping coordinate for each surface control point/vertex.
• kFBGeometryMapping_BY_POLYGON_VERTEX There will be one mapping coordinate for each vertex, for each polygon/strip it is part of. This means that a vertex will have as many mapping coordinates as polygons it is part of.
• kFBGeometryMapping_BY_POLYGON There can be only one mapping coordinate for the whole polygon/strip.
• kFBGeometryMapping_BY_EDGE There will be one mapping coordinate for each unique edge in the mesh. This is meant to be used with smoothing layer elements.
• kFBGeometryMapping_ALL_SAME There can be only one mapping coordinate for the whole surface.

See the C++ reference

Inheritance diagram for FBGeometryMappingMode:

Public Attributes
object	kFBGeometryMapping_NONE
object	kFBGeometryMapping_BY_CONTROL_POINT
object	kFBGeometryMapping_BY_POLYGON_VERTEX
object	kFBGeometryMapping_BY_POLYGON
object	kFBGeometryMapping_BY_EDGE
object	kFBGeometryMapping_ALL_SAME

Member Data Documentation

object kFBGeometryMapping_ALL_SAME

See the C++ reference

object kFBGeometryMapping_BY_CONTROL_POINT

See the C++ reference

object kFBGeometryMapping_BY_EDGE

See the C++ reference

object kFBGeometryMapping_BY_POLYGON

See the C++ reference

object kFBGeometryMapping_BY_POLYGON_VERTEX

See the C++ reference

object kFBGeometryMapping_NONE

See the C++ reference