As discussed with Sean on IRC, neither of us thinks the HID mappings really
should go to XML file anyway, at least not yet.
The way how HID works, sending packets with data for everything in one packet
and receiving state for all related controls in one packet, does not really fit
with the MIDI based control mapping functionality we had in midi.xml files. For
HID it is much more natural to have one stateful js script, which processes
all incoming HID data and sends the output packets in correct format. Stateful
meaning it keeps the button state packet ready, and on state changes, updates
the correct bits in the packet only and sends the new merged packet.
Still, if XML based input and output configuration for HID is expected, I hope
my long and complicated example XML file shows the problems we are expected to
see, and the side-effects regarding unnecessary functions calls triggered if we
are not careful with it.
For now, it's better to stick with 'write a stateful js script to receive and
send HID packets for your device' method, I think.
*hile*
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
