> It could also be useful to specify a range for midino. For example, many
> controllers have a series of 4 or 8 buttons in a row that could be
> mapped to one script function with one <control> XML element.
Maybe that would be useful in some scenarios. In my case it would not
be necessary because I'm using a dispatcher function anyway. I can
already do this with SYSEX messages, no?
If Mixxx could call this method (when it's defined) it would be the
easiest option. It could be made explicit by having a stanza that
diverts all messages like the example in my bug description, but that
would actually complicate matters as far as I'm concerned.
> It could also be useful to specify a range for midino. For example, many
> controllers have a series of 4 or 8 buttons in a row that could be
> mapped to one script function with one <control> XML element.
Maybe that would be useful in some scenarios. In my case it would not
be necessary because I'm using a dispatcher function anyway. I can
already do this with SYSEX messages, no?
SomeController. statusResponse = function(message) { /* handle SYSEX */ }
now I would like to generalize this to
SomeController. controllerMessa ge = function(message) { /* handle message */ }
If Mixxx could call this method (when it's defined) it would be the
easiest option. It could be made explicit by having a stanza that
diverts all messages like the example in my bug description, but that
would actually complicate matters as far as I'm concerned.