The SoFCSelectionAction class is used to inform an SoFCSelection node whether an object gets selected. More...
#include <SoFCSelectionAction.h>
Public Member Functions | |
SoFCSelectionAction (const SelectionChanges &SelCh) | |
~SoFCSelectionAction () | |
Static Public Member Functions | |
static void | finish (void) |
static void | initClass () |
The order of the defined SO_ACTION_ADD_METHOD statements is very important. | |
Public Attributes | |
const SelectionChanges & | SelChange |
Protected Member Functions | |
virtual void | beginTraversal (SoNode *node) |
The SoFCSelectionAction class is used to inform an SoFCSelection node whether an object gets selected.
Definition at line 46 of file SoFCSelectionAction.h.
SoFCSelectionAction::SoFCSelectionAction | ( | const SelectionChanges & | SelCh | ) |
Definition at line 159 of file SoFCSelectionAction.cpp.
SoFCSelectionAction::~SoFCSelectionAction | ( | ) |
Definition at line 166 of file SoFCSelectionAction.cpp.
void SoFCSelectionAction::beginTraversal | ( | SoNode * | node | ) | [protected, virtual] |
Definition at line 171 of file SoFCSelectionAction.cpp.
void SoFCSelectionAction::finish | ( | void | ) | [static] |
Definition at line 153 of file SoFCSelectionAction.cpp.
void SoFCSelectionAction::initClass | ( | void | ) | [static] |
The order of the defined SO_ACTION_ADD_METHOD statements is very important.
First the base classes and afterwards subclasses of them must be listed, otherwise the registered methods of subclasses will be overridden. For more details see the thread in the Coin3d forum https://www.coin3d.org/pipermail/coin-discuss/2004-May/004346.html. This means that SoSwitch
must be listed after SoGroup
and SoFCSelection
after SoSeparator
because both classes inherits the others.
Definition at line 107 of file SoFCSelectionAction.cpp.
Referenced by Gui::SoFCDB::init().
Definition at line 57 of file SoFCSelectionAction.h.
Referenced by Gui::SoFCUnifiedSelection::doAction(), and Gui::SoFCSelection::doAction().