MKtlElement : MAbstractElement : Object

Extension

The types of elements used in descs so far:MKtlElement.types; // to update after adding more desc files: MKtlDesc.loadDescs; MKtlDesc.elementTypesUsed;

Creates a new instance, with a name, a description and optionally a source.x = MKtlElement(\x, (spec: [-100, 100], type: \joyX, ioType: \in)); x.value = 0.42; x.value x.deviceValue

The source arg is usually an MKtl.

The spec that maps between the numerical value range the device sends and/or receives, and the the unipolar range in the MKtlElement.

The element's default value

Get and set the element's deviceValue in units and range of the deviceSpec

Get and set the element's current value in normalised range

Arguments:

Set the element's deviceValue or value without sending back to the hardware device

Set the element's deviceValue or value and perform its action.

Discussion:

deviceValue_ and value_ will not cause the action to be performed. deviceValueNoSend_ and valueNoSend_ will also not trigger the action.

If the element is has an output to send back to the device, value_ and deviceValue_ will send the deviceValue to the device, while deviceValueNoSend_ and valueNoSend_ allow just setting the value without sending it (which is sometimes necessary).

Example: Control a knob on the Behringer BCF2000// This will send the value to the device, causing the motorised fader to go to that position: MKtl('bcf1', "behringer-bcf2000"); MKtl('bcf1').elementsDict[\kn_1_1].value_(0.5); MKtl('bcf1').elementAt(\kn, 1, 1).deviceValue_(64); // This just sets the value in the MKtlElement: MKtl('bcf1').elementAt(\kn, 1, 1).valueNoSend_(0.5); MKtl('bcf1').elementAt(\kn, 1, 1).deviceValueNoSend_(64);

Add an action to the element's action. Adding multiple actions will create a FunctionList.

Remove an action from the list of current actions. The action to be removed has to be the exact same function object.

Perform the actions related to this element. This includes the action instance variable, and the actions of its parents, up to the containing MKtl.

Arguments:

ask whether this element's action is currently enabled

enable and disable this element's action. works hierarchically in MKtlElementGroup as well:make a g = MKtl(\fer, "*run*drive"); g.gui; g.dictAt(\wheel).action = { |el| [el.name, el.value.round(0.001)].postln }; g.elAt(\wheel).disable; g.elAt(\wheel).enable; // set action for bt group and bt_1: g.elAt(\bt).action = { |el| [\bt, el.name, el.value.round(0.001)].postln }; g.dictAt(\bt_1).action = { "yo, 1!".postln }; // bt1 posts from two actions! // disable group: bt1 posts its action, not group action g.elAt(\bt).disable; // disable bt 1, enable group: g.elAt(\bt, 0).disable; g.elAt(\bt).enable; // disable all individual button actions: g.elAt(\bt).do(_.enable);

Set action to nil.

pattern support - convert MKtlElement to a stream

pattern support - embed MKtlElement in a stream.// examples for direct pattern usage: MKtlDesc.postLoadable n = MKtl(\nk1, "korg-nanokontrol"); x = n.elementsDict[\play]; // the play button // test asStream method - simple endless lookup p = Pbind(\test, x).trace.play; // switch value while playing, pattern gets current value x.value = 1; x.value = 0; p.stop; // test embedInStream method: ( p = Pbind( \test, Pseq([x, 4, 7], 8), \dur, 0.5 ).trace.play; ) // change value while playing x.value = 1; x.value = 0; p.stop;

An Event or dictionary with a description of the element. Typically contains a deviceSpec, a type, and

Create a gui for this element.