CLAM::MIDIIOConfig Class Reference

Configuration of the MIDIIn and MIDIOut classes. More...

#include <MIDIIOConfig.hxx>

List of all members.

Public Member Functions

 DYNAMIC_TYPE_USING_INTERFACE (MIDIIOConfig, 4, ProcessingConfig)
 DYN_ATTRIBUTE (0, public, std::string, Device)
 The Device that will be used by this MIDIIn/Out instantiation, if it is not indicated, or its value is "default:default", system will choose the best device for this object.
 DYN_ATTRIBUTE (1, public, unsigned short, Message)
 The Message attribute allows you to create a MIDIOut that sends midi messages of a certain type.
 DYN_ATTRIBUTE (2, public, unsigned short, Channel)
 The Channel attribute allows you to create a MIDIOut that sends midi messages on a certain channel.
 DYN_ATTRIBUTE (3, public, unsigned short, FirstData)
 The Message attribute allows you to create a MIDIOut that sends midi messages with a certain first data byte (typically usefull for control messages).

Protected Member Functions

void DefaultInit (void)
 The concrete dynamic type constructor calls DefaultInit().


Detailed Description

Configuration of the MIDIIn and MIDIOut classes.

You can specify a device (string), which will be used by the MIDIManager, when creating the MIDIDevice objects. When you don't specify a concrete device, or specify "default", the MIDIManager will choose the default device for your setup.

See also:
MIDIIn, MIDIOut, MIDIDevice, MIDIManager, ProcessingConfig

Definition at line 37 of file MIDIIOConfig.hxx.


Member Function Documentation

void CLAM::MIDIIOConfig::DefaultInit ( void   )  [inline, 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().

See also:
CopyInit()

For MIDIIn 0 means: listen to all channels, and add an OutControl. For MIDIOut 0 means: channel is controlled by an InControl

For MIDIIn 128 means: listen to all first data bytes, and add an OutControl For MIDIOut 128 means: first data byte is controlled by an InControl

Reimplemented from CLAM::DynamicType.

Definition at line 65 of file MIDIIOConfig.hxx.

References CLAM::DynamicType::UpdateData().

CLAM::MIDIIOConfig::DYN_ATTRIBUTE ( ,
public  ,
unsigned  short,
FirstData   
)

The Message attribute allows you to create a MIDIOut that sends midi messages with a certain first data byte (typically usefull for control messages).

If you leave it 128 (default), an InControl will be created to control the first data byte.

CLAM::MIDIIOConfig::DYN_ATTRIBUTE ( ,
public  ,
unsigned  short,
Channel   
)

The Channel attribute allows you to create a MIDIOut that sends midi messages on a certain channel.

If you leave it 0 (default), an InControl will be created to control the channel of each MIDI message.

CLAM::MIDIIOConfig::DYN_ATTRIBUTE ( ,
public  ,
unsigned  short,
Message   
)

The Message attribute allows you to create a MIDIOut that sends midi messages of a certain type.

CLAM::MIDIIOConfig::DYN_ATTRIBUTE ( ,
public  ,
std::string  ,
Device   
)

The Device that will be used by this MIDIIn/Out instantiation, if it is not indicated, or its value is "default:default", system will choose the best device for this object.

CLAM::MIDIIOConfig::DYNAMIC_TYPE_USING_INTERFACE ( MIDIIOConfig  ,
,
ProcessingConfig   
)


The documentation for this class was generated from the following file:

Generated on Tue Feb 22 09:53:30 2011 for CLAM-Development by  doxygen 1.5.9