David Robillard
b1bc353f0d
Accordingly, make "generic" MIDI truly generic, just numbered controllers. Break up MIDI name UI stuff into manageable functions of reasonable size. Add convenient method to MIDINameDocument for getting the names for a device. Tolerate comments in MIDINameDocument ControlNameList. Can't remove the MIDI name code just yet, since it's still erroneously used by Automatable::describe_parameter(). This is the cause of a bug where the name on the automation lane does not match that in the menu. The plan is to make a very simple pure abstract interface for getting MIDI names, and make it possible to set one for Automatable (or perhaps pass it to describe_parameter()). Thus we'll be on the way to supporting names from sources other than midnam files, namely plugins. git-svn-id: svn://localhost/ardour2/branches/3.0@13895 d708f5d6-7413-0410-9779-e7cbd77b26cf |
||
---|---|---|
.. | ||
macosx | ||
midi++ | ||
test | ||
.cvsignore | ||
channel.cc | ||
COPYING | ||
ipmidi_port.cc | ||
jack_midi_port.cc | ||
libmidi++.pc.in | ||
libmidi++.spec.in | ||
manager.cc | ||
midi.cc | ||
miditrace.cc | ||
midnam_patch.cc | ||
mmc.cc | ||
mmctest.cc | ||
mtc.cc | ||
parser.cc | ||
port.cc | ||
run-tests.sh | ||
wscript |