#include <SMSHarmonizerConfig.hxx>
Definition at line 33 of file SMSHarmonizerConfig.hxx.
Public Member Functions | |
DYNAMIC_TYPE_USING_INTERFACE (SMSHarmonizerConfig, 2, ProcessingConfig) | |
DYN_ATTRIBUTE (0, public, int, NumberOfVoices) | |
DYN_ATTRIBUTE (1, public, bool, IgnoreResidual) | |
Protected Member Functions | |
void | DefaultInit () |
The concrete dynamic type constructor calls DefaultInit(). |
CLAM::SMSHarmonizerConfig::DYNAMIC_TYPE_USING_INTERFACE | ( | SMSHarmonizerConfig | , | |
2 | , | |||
ProcessingConfig | ||||
) |
CLAM::SMSHarmonizerConfig::DYN_ATTRIBUTE | ( | 0 | , | |
public | , | |||
int | , | |||
NumberOfVoices | ||||
) |
CLAM::SMSHarmonizerConfig::DYN_ATTRIBUTE | ( | 1 | , | |
public | , | |||
bool | , | |||
IgnoreResidual | ||||
) |
void CLAM::SMSHarmonizerConfig::DefaultInit | ( | void | ) | [protected] |
The concrete dynamic type constructor calls DefaultInit().
This allows user to initialize his/her object. But we define DefaultInit() here because we don't want to force writting one DefaultInit() function for each concrete dynamic type. If a dynamic type concrete class defines some (not-default) constructors, this should also call the DefaultInit().
Reimplemented from CLAM::DynamicType.
Definition at line 26 of file SMSHarmonizerConfig.cxx.
References CLAM::DynamicType::UpdateData().