Adam Davison wrote: > For this reason I would prefer us not to accept code unless we can see > that clearly this is going to be useful for lots of controllers, rather > than it being code that just makes this particular one work.
Oh, I completely agree. That's why I'm trying to keep this within the confines of the XML file. Adding controller-specific stuff to the Mixxx code was Albert's idea. ;P > If we want to avoid using full scripting for at least some things, > then clearly we need to add some more programmability to the XML. Exactly. (I was originally asking if this already existed.) I need state variable setting & checking, conditional XML inclusion (i.e. while deviceMode!=1, then ignore these <control> and <output> (<light>) definitions,) basic arithmetic, and the ability to send (ideally arbitrary) strings of bytes to the MIDI device (sometimes conditional.) But if it's much easier (from a Mixxx coding standpoint) to just use full scripting, then I'm cool with that. So how soon can something be implemented?? :D Sean "D.J. Pegasus" <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
