561
edits
(→Build System: We got a tool which creates MSVC project files out of configure / module.mk now (not in perl though ;-).) |
m (→MIDI: mention that Kyra has more complete XMIDI implementation too.) |
||
Line 108: | Line 108: | ||
**This doesn't allow for easy tweaking of those settings via the GUI.... to achieve that, one approach would be to invent a 'parameter description language' which allows a driver to specify which options with which kind of values it supports... very flexible, but possibly overkill. | **This doesn't allow for easy tweaking of those settings via the GUI.... to achieve that, one approach would be to invent a 'parameter description language' which allows a driver to specify which options with which kind of values it supports... very flexible, but possibly overkill. | ||
**Instead, one could add a hook method to MIDI drivers that let's them add a few controls of their own to the options dialog. This is probably a lot easier to implement, though not quite as "clean"... | **Instead, one could add a hook method to MIDI drivers that let's them add a few controls of their own to the options dialog. This is probably a lot easier to implement, though not quite as "clean"... | ||
* Our XMIDI parser seems to have a couple of missing features, but it's unclear which ones are actually needed. Possible references for a better implementation include the [http://exult.sf.net Exult] project and the [http://www.thegleam.com/ke5fx/ source code for AIL Version 2]. | * Our XMIDI parser seems to have a couple of missing features, but it's unclear which ones are actually needed. Possible references for a better implementation include the [http://exult.sf.net Exult] project and the [http://www.thegleam.com/ke5fx/ source code for AIL Version 2]. The KYRA engine implements some more complete XMIDI implementation on top of our XMIDI parser class too, so it might also be a place to look at for reference. | ||
=== Config Manager === | === Config Manager === |
edits