HDK
|
Helpers for working with Gf types (vectors, matrices, etc.) within the HDK. More...
#include <UT_Gf.h>
Classes | |
struct | Castable |
struct | TypeEquivalence |
Static Public Member Functions | |
template<class FROM , class TO > | |
static void | Convert (const FROM &from, TO &to) |
template<class T > | |
static const TypeEquivalence < T >::AltType * | Cast (const T *val) |
template<class T > | |
static TypeEquivalence< T > ::AltType * | Cast (T *val) |
template<class T > | |
static const TypeEquivalence < T >::AltType & | Cast (const T &val) |
template<class T > | |
static TypeEquivalence< T > ::AltType & | Cast (T &val) |
template<class FROM , class TO > | |
static const TO * | Cast (const FROM *val) |
template<class FROM , class TO > | |
static TO * | Cast (FROM *val) |
template<class FROM , class TO > | |
static const TO & | Cast (const FROM &val) |
template<class FROM , class TO > | |
static TO & | Cast (FROM &val) |
template<class T > | |
static void | Convert (const GfQuaternion &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const GfQuatd &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const GfQuatf &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const GfQuath &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const GfVec4d &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const GfVec4f &from, UT_QuaternionT< T > &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfQuaternion &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfQuatd &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfQuatf &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfQuath &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfVec4d &to) |
template<class T > | |
static void | Convert (const UT_QuaternionT< T > &from, GfVec4f &to) |
Helpers for working with Gf types (vectors, matrices, etc.) within the HDK.
|
inlinestatic |
Helpers for casting between UT and Gf types. The cast can go either way. This can be done with a reinterpret cast, but this cast adds a bit of extra compile-time checks to make sure that this really is safe.
These cast methods only take a single template argument. The output is cast to the equivalent type from the alternate API. For example, if given a UT_Matrix4D, the cast is to a GfMatrix4d, and vice versa.
Examples:
|
inlinestatic |
Helpers for casting between UT and Gf types. The cast can go either way. This can be done with a reinterpret cast, but this cast adds a bit of extra compile-time checks to make sure that this really is safe.
These cast methods only take a single template argument. The output is cast to the equivalent type from the alternate API. For example, if given a UT_Matrix4D, the cast is to a GfMatrix4d, and vice versa.
Examples:
|
inlinestatic |
Helpers for casting between UT and Gf types. The cast can go either way. This can be done with a reinterpret cast, but this cast adds a bit of extra compile-time checks to make sure that this really is safe.
These cast methods only take a single template argument. The output is cast to the equivalent type from the alternate API. For example, if given a UT_Matrix4D, the cast is to a GfMatrix4d, and vice versa.
Examples:
|
inlinestatic |
Helpers for casting between UT and Gf types. The cast can go either way. This can be done with a reinterpret cast, but this cast adds a bit of extra compile-time checks to make sure that this really is safe.
These cast methods only take a single template argument. The output is cast to the equivalent type from the alternate API. For example, if given a UT_Matrix4D, the cast is to a GfMatrix4d, and vice versa.
Examples:
|
inlinestatic |
Explicit casts between UT and Gf types. This is just like the implicit cast methods, except that the source and target types are explicitly specified via template arguments. This can be used for casting between types when the types aren't exact counterparts. For instance, we can safely cast a GfMatrix2d to a UT_Vector4D, even though UT_Vector4D is not UT's equivalence type for GfMatrix2d.
|
inlinestatic |
Explicit casts between UT and Gf types. This is just like the implicit cast methods, except that the source and target types are explicitly specified via template arguments. This can be used for casting between types when the types aren't exact counterparts. For instance, we can safely cast a GfMatrix2d to a UT_Vector4D, even though UT_Vector4D is not UT's equivalence type for GfMatrix2d.
|
inlinestatic |
Explicit casts between UT and Gf types. This is just like the implicit cast methods, except that the source and target types are explicitly specified via template arguments. This can be used for casting between types when the types aren't exact counterparts. For instance, we can safely cast a GfMatrix2d to a UT_Vector4D, even though UT_Vector4D is not UT's equivalence type for GfMatrix2d.
|
inlinestatic |
Explicit casts between UT and Gf types. This is just like the implicit cast methods, except that the source and target types are explicitly specified via template arguments. This can be used for casting between types when the types aren't exact counterparts. For instance, we can safely cast a GfMatrix2d to a UT_Vector4D, even though UT_Vector4D is not UT's equivalence type for GfMatrix2d.
|
inlinestatic |
Convert between UT and Gf types. This works for any pod tuples that have equivalent tuple sizes, even if their underlying precision differs.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.
|
inlinestatic |
Conversions between GF and UT quaternions. Gf and UT have a different ordering of the real component, hence the need for speciailized converters.
XXX: 4d vector types are sometimes used in place of GfQuaternion, hence their inclusion here. That is primarily the fault of USD: if USD gets a real quaternion type, we can clean these up.