On 07/06/2015 05:02 PM, Be wrote: > Yes, I think the gap between making simple mappings and programming > should be bridged, kind of like how shell scripting is not really > different from just using the shell. A large amount of the code in the > Electrix Tweaker mapping I wrote, and likely most JS mappings, is simple > functions that just check the value of a modifier or engine state then > change one Mixxx control with engine.setValue depending on those > conditions. It would reduce code duplication and I think be more > intuitively organized to have functions that respond to modifier buttons > and change the appropriate mapping objects.
I realized a simpler way to do this: define layers in XML. This approach would build upon the current XML format and probably wouldn't be too difficult to modify the GUI to use. Instead of single global <controls> and <outputs> elements, make these elements children of <layer> elements. There could still be a <controls> and <outputs> elements for mapping buttons that toggle different layers and controls that are always the same. There would need to be ------------------------------------------------------------------------------ _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
