I've been hacking away frantically at this new MIDI branch, and I'm stuck. We have a MidiMapping class that contains what is essentially a map between MIDI messages and ControlObjects, but it doesn't actually get used outside the GUI stuff yet. All of the "mapping" still takes place in MidiObject and ConfigObject. I'm trying to fix this.
The problem I've got is that there's still all this weird translation stuff going on in ConfigObject. See ConfigValueMidi::ComputeValue() in configobject.cpp. I think I'm going to move that code out of there and into MidiMapping, so that the mapping does the required transformations. All of the "translation" code is going to break, and I'm not interested in replacing it at the moment because I think scripting is the right way to do it. Yeah, so... I'm going to try to continue sanitizing the way the mapping stuff works, but it has the potential to break a lot of things. There's a disproportionate amount of hacks in the code to support the Xponent, so that's definitely going to break as I remove them. Albert ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
