Hi! Melchior FRANZ wrote: > (2) I'd say that we want to keep the power of XML defined > bindings (with embedded Nasal where appropriate.) But > one could think about not having those automatically > triggered, but read them into a map, and let the > keys trigger such bindings by name. That way one could > assign bindings in a dialog. (Personally, I don't like > this type of configuration at all. It's not nearly > as flexible as editing the XML file, and one doesn't > configure the keyboard often, especially if the > defaults are sane. This is just a lot of bloat and > complexity for a feature that isn't needed at runtime > at all.)
Hm, wouldn't that - in UNIX manner - call for an external configuration tool to edit the XML bindings? I'm putting this here without ever having thought of who would actually take the effort ;-) It's not unreasonable to assume that such a solution would require more effort than modifying the keyboard binding mechanism as you suggested. Cheers, Ralf ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
