DirectOutputR1
DirectOutput framework R1 for virtual pinball cabinets.
|
Go to: Overview |
Implementation of a generic analog toy. Implements IToy.
A configuration section for AnalogToy might resemble the following structure:
AnalogToy has the following 2 configurable properties:
The name of the item.
Name of the Output for the GenericAnalogToy.
Contactor toy. Basicaly just a more descriptive name for a GenericDigitalToy. Implements IToy, inherits GenericDigitalToy
A configuration section for Contactor might resemble the following structure:
Contactor has the following 2 configurable properties:
The name of the item.
Name of the Output for the GenericDigitalToy
Implementation of a generic digital toy. Implements IToy.
A configuration section for DigitalToy might resemble the following structure:
DigitalToy has the following 2 configurable properties:
The name of the item.
Name of the Output for the GenericDigitalToy
GearMotor toy is just a simple wrapper around the Motor toy.
A configuration section for GearMotor might resemble the following structure:
GearMotor has the following 7 configurable properties:
The kickstart duration in milliseconds.
The kickstart power for the motor.
The maximum power for the motor.
The max run time in milliseconds.
The minimal power for the motor.
The name of the item.
Name of the Output for the GenericAnalogToy.
Lamp toy.
Inherits from T:DirectOutput.Cab.Toys.Basic.AnalogToy, implements T:DirectOutput.Cab.Toys.IToy.
A configuration section for Lamp might resemble the following structure:
Lamp has the following 2 configurable properties:
The name of the item.
Name of the Output for the GenericAnalogToy.
Motor toy supporting max. and min. power, max. runtime and kickstart settings.
Inherits from GenericAnalogToy, implements IToy.
A configuration section for Motor might resemble the following structure:
Motor has the following 7 configurable properties:
The kickstart duration in milliseconds.
The kickstart power for the motor.
The maximum power for the motor.
The max run time in milliseconds.
The minimal power for the motor.
The name of the item.
Name of the Output for the GenericAnalogToy.
RGB led toy controlls a multicolor led. Implement IToy, inherits Toy.
A configuration section for RGBLed might resemble the following structure:
RGBLed has the following 4 configurable properties:
The name of the item.
Name of the IOutput for blue.
Name of the IOutput for green.
Name of the IOutput for red.
Shaker toy.
This is just a simple wrapper around the motor toy.
Inherits from GenericAnalogToy, implements IToy.
A configuration section for Shaker might resemble the following structure:
Shaker has the following 7 configurable properties:
The kickstart duration in milliseconds.
The kickstart power for the motor.
The maximum power for the motor.
The max run time in milliseconds.
The minimal power for the motor.
The name of the item.
Name of the Output for the GenericAnalogToy.
This toy handles analog values (0-255) in a layer structure including alpha value (0=completely transparent, 255=fully opaque) and outputs the belended result of the layers on a single output.
A configuration section for AnalogAlphaToy might resemble the following structure:
AnalogAlphaToy has the following 2 configurable properties:
The name of the item.
The name of the output.
Thie RGBAToy controls RGB leds and other gadgets displaying RGB colors.
The RGBAToy has multilayer support with alpha channels. This allows the effects targeting RGBAToys to send their data to different layers. Values in a layer do also have a alpha/transparency channel which will allow us to blend the colors/values in the various layers (e.g. if a bottom layer is blue and top is a semi transparent red, you will get some mix of both or if one of the two blinks you get changing colors).
The following picture might give you a clearer idea how the layers with their alpha channels work:
A configuration section for RGBAToy might resemble the following structure:
RGBAToy has the following 4 configurable properties:
The name of the item.
Name of the IOutput for blue.
Name of the IOutput for green.
Name of the IOutput for red.
The LEDWizEquivalent toy is only used by the framework when ini files are used for the configuration to determine which outputs should be controled by the columns in the ini files.
Do not target this type of toy with any effects.
A configuration section for LedWizEquivalent might resemble the following structure:
LedWizEquivalent has the following 3 configurable properties:
The number of the virtual LedWiz resp. ini file to be matched with the LedWizEquivalentToy.
The name of the item.
The outputs of the LedWizEquivalent toy.
Nested Properties
The following nested propteries exist for Outputs: