The SoCylinderDetail class contains information about the parts of a SoCylinder shape.
More...
#include <Inventor/details/SoCylinderDetail.h>
The SoCylinderDetail class contains information about the parts of a SoCylinder shape.
Instances of this class are used for storing information about hit points on cylinder geometry after pick operations, and for storing information returned to tessellation callbacks.
- See also
- SoCylinder, SoRayPickAction, SoCallbackAction
◆ SoCylinderDetail()
SoCylinderDetail::SoCylinderDetail |
( |
void |
| ) |
|
◆ ~SoCylinderDetail()
SoCylinderDetail::~SoCylinderDetail |
( |
| ) |
|
|
virtual |
◆ getTypeId()
SoType SoCylinderDetail::getTypeId |
( |
void |
| ) |
const |
|
virtual |
Returns the type identification of an object derived from a class inheriting SoDetail. This is used for runtime type checking and "downward" casting.
Implements SoDetail.
◆ getClassTypeId()
SoType SoCylinderDetail::getClassTypeId |
( |
void |
| ) |
|
|
static |
This static method returns the SoType object associated with objects of this class.
◆ cleanupClass()
static void SoCylinderDetail::cleanupClass |
( |
void |
| ) |
|
|
inlinestatic |
This static method cleans up static data of the class.
◆ initClass()
void SoCylinderDetail::initClass |
( |
void |
| ) |
|
|
static |
◆ copy()
SoDetail * SoCylinderDetail::copy |
( |
void |
| ) |
const |
|
virtual |
Return a deep copy of ourself.
Note that if the Coin library has been built as a DLL under Microsoft Windows and you use this method from application code, you must make sure that both the Coin DLL and the application executable are using the same instance of a C Run-Time (CRT) library. Otherwise, you will get memory heap corruption upon deallocating the returned instances, eventually leading to mysterious crashes.
Implements SoDetail.
◆ setPart()
void SoCylinderDetail::setPart |
( |
const int |
partarg | ) |
|
◆ getPart()
int SoCylinderDetail::getPart |
( |
void |
| ) |
const |
Returns selected cylinder part.
◆ part
int SoCylinderDetail::part |
|
protected |
This API member is considered internal to the library, as it is not likely to be of interest to the application programmer.
The documentation for this class was generated from the following files: