The canvas is a two-dimensional table of CanvasPoints which can be resized.

Changelog

0.99.5 - (new), enable/disable (MIDI) message throttling

0.99.3 - (new), match a specific (CC) value - from, @matchto> (new), match a (CC) value-range - (new), specify resolution (7/14 bit) and operation (absolute/relative) - (new), interpret parameter in the context of a specific device class

0.99.2 - Faster, more flexible parameter matching - all messages are processed on startup, cached/memoized where possible - OSC patterns now support "captures", see getoscparams() for more info - getoscparams(): when using wildcards, returns table of regexp-matches - (new), allows inverting the value (flip min/max) - (new) update device only when changed via virtual UI - (new), specify the font type - relevant for @type=labels only - attribute has been retired - attribute has been retired, just enter a blank @value - widget type has been retired (use @type="button") - new node type for combining several parameters into one (finally, we can have a "proper" xypad control for MIDI devices) - (new), set to false to hide the entire group

0.99.1 - TWEAK No more need to explicitly state "is_virtual" for parameters that only exist in the virtual UI - just leave the value attribute blank

0.98.14 - cache parameters

o Faster retrieval of MIDI parameters (put in cache once requested)

- New input method xypad, for creating XYPad controls in the virtual control surface (paired-value support, however only OSC devices can define this input method) - new input method: key - for accepting note-input from individual buttons/pads (Note: OBSOLETE) - Control-map/virtual control surface: keyboard - a new input method for representing a keyboard (the control surface will draw a series of keys)

o In the control-map, you can specify it`s range (number of keys)

- Control-map/XML parsing:

o Attribute names can now contain underscore

- Control-map/note value syntax: octave wildcard - you can now put an asterisk in place of the octave to make mapping respond to the note only (e.g.

Display performs many duties; it manages UIComponents, as it will both send and recieve their messages, and take care of their visual updates on the idle time update.

The purpose is to keep track of active voices, and their context: how the note got triggered: which device/application/instrument/pitch etc.

Device and application setup for controllers are registered by the controllers itself.