Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
Hello Vivian, Am Samstag, den 10.11.2007, 19:37 + schrieb Vivian Meazza: 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 On sam 10 novembre 2007, David Megginson wrote: On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David Oh, i am only like the dog which try to catch his tail. Since we had the 'L used with carrier , (this was talked before), i only 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. The F4U-1 doesn't use the launchbar. It toggles the Tailwheel lock by Ctrl-L, so l for lighting, L for Launchbar and Ctrl-l for Tailwheel lock would work. However I would follow every agreement on key usage. 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 Greetings Detlef - 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 - 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
gerard robin Sent: 11 November 2007 13:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml,1.99, 1.100 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 Not really, later on in the YASim config, it's ignored. Vivian - 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On dim 11 novembre 2007, Vivian Meazza wrote: gerard robin Sent: 11 November 2007 13:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml,1.99, 1.100 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 Not really, later on in the YASim config, it's ignored. Vivian Oh, right, thanks. So the nice way, mainly for carrier is to ignore the keyboard.xml , and to create some specific key dedicated to the Aircraft. My apologizes (mainly to David) for that noise which came first from me. In that case the L l could be used for any other features: = light , livery and so on. Regards -- 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On sam 10 novembre 2007, David Megginson wrote: Update of /var/cvs/FlightGear-0.9/data In directory baron:/tmp/cvs-serv32383 Modified Files: keyboard.xml Log Message: Reassign tail-wheel locking from 'l' to 'L' (previously unused), and use 'l' to toggle lighting. Index: keyboard.xml === RCS file: /var/cvs/FlightGear-0.9/data/keyboard.xml,v retrieving revision 1.99 retrieving revision 1.100 diff -C 2 -r1.99 -r1.100 *** keyboard.xml 1 Aug 2007 08:20:21 - 1.99 --- keyboard.xml 10 Nov 2007 01:30:04 - 1.100 *** *** 625,628 --- 625,637 /key + key n=76 + nameL/name + descToggle tail-wheel lock./desc + binding +commandproperty-toggle/command +property/controls/gear/tailwheel-lock/property + /binding + /key + key n=77 nameM/name *** *** 856,863 key n=108 namel/name ! descToggle tail-wheel lock./desc binding !commandproperty-toggle/command !property/controls/gear/tailwheel-lock/property /binding /key --- 865,872 key n=108 namel/name ! descTurn on aircraft panel lighting./desc binding !commandnasal/command !scriptcontrols.toggleLights()/script /binding /key I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) Regards -- 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David - 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On sam 10 novembre 2007, David Megginson wrote: On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David Oh, i am only like the dog which try to catch his tail. Since we had the 'L used with carrier , (this was talked before), i only 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. Regards -- 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
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
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 On sam 10 novembre 2007, David Megginson wrote: On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David Oh, i am only like the dog which try to catch his tail. Since we had the 'L used with carrier , (this was talked before), i only 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 - 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
