SemanticsSemanticsAPI#
Fully qualified name: usdrt::SemanticsSemanticsAPI
-
class SemanticsSemanticsAPI : public usdrt::UsdAPISchemaBase#
Public Functions
- inline explicit SemanticsSemanticsAPI( )#
Construct a SemanticsSemanticsAPI on UsdPrim
prim
with namename
. Equivalent to SemanticsSemanticsAPI::Get( prim.GetStage(), prim.GetPath().AppendProperty( “semantic:name”));.for a valid
prim
, but will not immediately throw an error for an invalidprim
- inline explicit SemanticsSemanticsAPI(
- const UsdSchemaBase &schemaObj,
- const TfToken &name,
Construct a SemanticsSemanticsAPI on the prim held by
schemaObj
with namename
. Should be preferred over SemanticsSemanticsAPI(schemaObj.GetPrim(), name), as it preserves SchemaBase state.
-
inline virtual ~SemanticsSemanticsAPI()#
Destructor.
-
inline UsdAttribute GetSemanticTypeAttr() const#
String value of the semantic type.
Declaration
string params:semanticType
C++ Type
std::string
Usd Type
SdfValueTypeNames->String
-
inline UsdAttribute CreateSemanticTypeAttr() const#
See GetSemanticTypeAttr(), and also Create vs Get Property Methods for when to use Get vs Create. If specified, author
defaultValue
as the attribute’s default, sparsely (when it makes sense to do so) ifwriteSparsely
istrue
- the default forwriteSparsely
isfalse
.
-
inline UsdAttribute GetSemanticDataAttr() const#
String value of the semantic data.
Declaration
string params:semanticData
C++ Type
std::string
Usd Type
SdfValueTypeNames->String
-
inline UsdAttribute CreateSemanticDataAttr() const#
See GetSemanticDataAttr(), and also Create vs Get Property Methods for when to use Get vs Create. If specified, author
defaultValue
as the attribute’s default, sparsely (when it makes sense to do so) ifwriteSparsely
istrue
- the default forwriteSparsely
isfalse
.
-
inline explicit operator bool() const#
Check if this schema object is compatible with it’s held prim and that the prim is valid.
A typed schema object is compatible if the held prim’s type is or is a subtype of the schema’s type. Based on
prim.IsA()
.An API schema object is compatible if the API is of type SingleApplyAPI or UsdSchemaType::MultipleApplyAPI, and the schema has been applied to the prim. Based on
prim.HasAPI
.This method invokes polymorphic behaviour.
See also
- Returns:
True if the help prim is valid, and the schema object is compatible with its held prim.
Public Static Functions
- static inline SemanticsSemanticsAPI Apply( )#
Applies this multiple-apply API schema to the given
prim
along with the given instance name,name
.This information is stored by adding “SemanticsAPI:<i>name</i>” to the token-valued, listOp metadata apiSchemas on the prim. For example, if
name
is ‘instance1’, the token ‘SemanticsAPI:instance1’ is added to ‘apiSchemas’.See also
See also
See also
See also
- Returns:
A valid SemanticsSemanticsAPI object is returned upon success. An invalid (or empty) SemanticsSemanticsAPI object is returned upon failure. See UsdPrim::ApplyAPI() for conditions resulting in failure.
Public Static Attributes
-
static const UsdSchemaType schemaType = UsdSchemaType::MultipleApplyAPI#
Compile time constant representing what kind of schema this class is.
See also
Protected Functions
-
inline const TfToken &_GetInstanceName() const#
Returns the instance name of the API schema object belonging to a multiple-apply API schema.
The returned instance name will be empty for non-applied and single-apply API schemas.
-
inline virtual bool _IsCompatible() const#
Check whether this APISchema object is valid for the currently held prim.
If this is an applied API schema, this returns true if the held prim is valid and already has the API schema applied to it, along with the instanceName (in the case of multiple-apply). The instanceName should not be empty in the case of a multiple-apply API schema.
This check is performed when clients invoke the explicit bool conversion operator, implemented in UsdSchemaBase.
See also