On sam 10 novembre 2007, Vivian Meazza wrote: > gerard robin > > > Sent: 10 November 2007 18:37 > > To: FlightGear developers discussions > > Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: > > data keyboard.xml,1.99, 1.100 > > > > > wonder if it would not have been better to find a global > > agreement on > > which "key" can do what, before to make that update. > > > > There is some aircraft within CVS which are carrier compatible. > > > > With that update the launchbar will not work now. > > Should be OK, the carrier bindings will over-write the keyboard bindings. > It will be a problem if there is an aircraft with both tail wheel lock > _and_ carrier launch bar (F4U?) I haven't checked that. > > And perhaps we can come up with a long term solution. I'm sure Melchior's > little grey cells are working overtime. > > Still, perhaps we shouldn't be making changes until we are clearer about > the consequences. > > Vivian > >
I did not check it , but your Seafire has both Launchbar and tailwheel lock, What is the matter now with the keyboard updated ? Regard -- Gérard http://pagesperso-orange.fr/GRTux/ ------------------------------------------------------------------------- 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
