Should we reserve a set of keys to be used in aircraft-set files? We already have Ctrl-B and C that I know of, and I'm working on a plane that will have at least one aircraft specific control. Do we leave it up to the code developers to know all of the aircraft so they don't step on existing aircraft specific keys when adding some new funcionality to flightgear, or would it be smart to agree on some set of reserved keys? That way aircraft designers won't have to worry about conflicts with future additions to Flightgear. All this really has to be is a piece of documentation so everybody knows what to expect in the future. It would also be helpful for people who like to configure their own keyboard layout and don't want to clobber some neat toy in an airplane model that is yet to be built.
Jim suggested to leave the ctrl key bindings to be aircraft specific, and I like this idea. Lets define the ctrl combinations for actions that are not available in every aircraft (speedbrake, engine boost, drag-chute, thrust reverse, etc).
Erik
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
