Re: [Flightgear-devel] Minor keyboard reassignment
* SydSandy -- Saturday 10 November 2007: Melchior FRANZ [EMAIL PROTECTED] wrote: Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Im not sure what you mean by exaggerated , Keys that don't require you to also press a modifier key are (very obviously) easier to access than key combinations. And a livery change is the last thing where we need quick and easy access. This could be on one of the F[0-9]* keys, or even a menu only function. m. - 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] Minor keyboard reassignment
While you are re-assigning keys, can I suggest that we remove t/T for the time-warp and reassign that to either a ctrl combo or a menu item. It doesnt strike me that this is a function thats needed in a hurry like a flight control or switch. Possibly ''t and its friends could get re-assigned to turbine start/shutdown? Its not the first time Ive screwed up a long flight by accidentally hitting 't' and getting thoroughly confused. A standard keyboard assignment for carb heat would be useful too (and much more relevant for myself and Im guessing 90+% of the users who actually get to fly real aircraft) and add greatly to the realism. I know there are aircraft where we have a clickable hot-spot for the carb heat but its usually difficult to find and a hassle. Carb heat should be like backups -- make it easy and folk will do it - forget about it and you will have big trouble sooner or later. --- Best Regards Willie Fleming [EMAIL PROTECTED] - 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] Minor keyboard reassignment
Willie Fleming schrieb: While you are re-assigning keys, can I suggest that we remove t/T for the time-warp and reassign that to either a ctrl combo or a menu item. It doesnt strike me that this is a function thats needed in a hurry like a flight control or switch. Possibly ''t and its friends could get re-assigned to turbine start/shutdown? Its not the first time Ive screwed up a long flight by accidentally hitting 't' and getting thoroughly confused. Yes, Willie, I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. So I always had to cancel the flight. This dangerous key assignment should be changed for some more beneficial for daily use. Georg EDDW - 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] Minor keyboard reassignment
* Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. m. - 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] Minor keyboard reassignment
Melchior FRANZ schrieb: * Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. m. Thank you for this clarification which can save my day sometime in the future but thinking of many other users not reading this list it could be a good idea to hide the time-warping function a little more. Georg - 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] Minor keyboard reassignment
* Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) m. - 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] Minor keyboard reassignment
On Sun, 11 Nov 2007 11:06:42 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 10 November 2007: Melchior FRANZ [EMAIL PROTECTED] wrote: Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Im not sure what you mean by exaggerated , Keys that don't require you to also press a modifier key are (very obviously) easier to access than key combinations. And a livery change is the last thing where we need quick and easy access. This could be on one of the F[0-9]* keys, or even a menu only function. m. ok , I understand now . It was mainly meant for testing ... I tried to use the material animation based on a /sim/model/variant condition , but that only works once , in one direction , that is , liveries will change until you toggle the last one , then that's where it stays . I'm guessing tthats because of the material animations limitation on changing the same object(s) more than once ... But I'm still working on it (and lets face it , its easier to get a response when I screw things up, rather than ask a question ;) ) Cheers -- SydSandy [EMAIL PROTECTED] - 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] Minor keyboard reassignment
On Sun, 11 Nov 2007 19:06:14 +0100 Georg Vollnhals [EMAIL PROTECTED] wrote: Melchior FRANZ schrieb: * Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. m. Thank you for this clarification which can save my day sometime in the future but thinking of many other users not reading this list it could be a good idea to hide the time-warping function a little more. Georg Just here to add my vote I've done the accidental time warp too , very confusing if you hit it once and dont have a clock installed yet :) .I agree that it should be moved out of the way ... or removed completely , since you can set the time of day on the commandline or FGrun ... Cheers -- SydSandy [EMAIL PROTECTED] - 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] Minor keyboard reassignment
On Sunday 11 November 2007 18:07:24 Melchior FRANZ wrote: * Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Reasoning behind the toggle - for proper use of the carb heat you want to have it on for 30-60 secs in the cruise and on anytime the throttle is less than 50% open. At least thats the way its taught at our club and we haven't lost an aircraft to carb icing since this rule was introduced. Please don't ask what happened before this rule was brought in Anybody else with me on this? --- Best Regards Willie Fleming [EMAIL PROTECTED] - 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] Minor keyboard reassignment
Willie Fleming schrieb: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Reasoning behind the toggle - for proper use of the carb heat you want to have it on for 30-60 secs in the cruise and on anytime the throttle is less than 50% open. At least thats the way its taught at our club and we haven't lost an aircraft to carb icing since this rule was introduced. Please don't ask what happened before this rule was brought in Anybody else with me on this? My vote for it Georg --- Best Regards Willie Fleming - 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] Minor keyboard reassignment
On Nov 11, 2007 12:30 PM, Willie Fleming wrote: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) I don't disagree with any of this, timewarp probably doesn't deserve it's own pair of keystrokes. However, blindly assigning it to a menu item might cause us to lose the ability to do any fine grain nudging of the time forward or back. Maybe I'm the only one that does that? But for whomever decides to reassign this functionality to a menu entry, I'd like to see maybe a dialog box where you can advance/rewind the time by 60 seconds, 5 minutes, 1 hour, etc. along with setting the time to specific periods of the day (noon, dusk, etc.) Perhaps even be able to manually enter a time offset (warp value) in seconds. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - 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] Minor keyboard reassignment
On Sunday 11 November 2007 19:07, Melchior FRANZ wrote: * Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) m. Funny, I was thinking exactly the same earlier this week. The t/T combination dates back from the very early days of FlightGear, when they had their use. Those days are long gone. To me it seems that this would be something useful for a menu or dialog box. Not something for an easy accessible hotkey. Cheers, Durk - 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] Minor keyboard reassignment
* Curtis Olson -- Sunday 11 November 2007: I don't disagree with any of this, timewarp probably doesn't deserve it's own pair of keystrokes. I use this often and definitely want a key for it. Only 't' seems a bit too wasteful and dangerous. (But I can also make my own local key definition for it. I have lots of free keys, thanks to my use of the Meta modifier. :-) m. - 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] Minor keyboard reassignment
* Willie Fleming -- Sunday 11 November 2007: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Of course you have to offer solutions for the keys that you want replaced. h is the HUD. And what are your plans for the former t/T warp function? It quickly becomes less fun when you have to consider that. Have a look at $FG_ROOT/Docs/keyboard/map.pdf for inspiration. :-) m. - 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] Minor keyboard reassignment
On sam 10 novembre 2007, Melchior FRANZ wrote: * Melchior FRANZ -- Saturday 10 November 2007: L is used to engage in the aircraft carrier's catapult (see $FG_ROOT/Input/Keyboard/carrier-bindings.xml). So around 10 aircraft will overwrite the new lighting binding anyway. err ... the tailwheel lock binding. (I didn't even know that it was there. I have that on my js.) We have still several keys globally unassigned, but it's increasingly hard to find one that isn't used by at least one aircraft. In the long run we'll have to reorganize a bit. We waste a lot of keys for obscure features that a typical simulator user will never need and/or that are too easy to press by accident (a/A, t/T, r, ...). The carrier bindings could IMHO be in a small popup dialog (like the ATC dialog). They aren't for controlling the aircraft after all, but to give orders to the carrier crew. m. Anyhow, i am not sure it would be a good idea to use the reserved carrier KEYS. There is only a the little number of persons who use and like the carriers, which is not the majority of the FG community :(, so i can understand that many persons don't mind about carrier, and i worry it. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). Please keep it. 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] Minor keyboard reassignment
Gerard robin wrote Sent: 10 November 2007 09:29 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Minor keyboard reassignment On sam 10 novembre 2007, Melchior FRANZ wrote: * Melchior FRANZ -- Saturday 10 November 2007: L is used to engage in the aircraft carrier's catapult (see $FG_ROOT/Input/Keyboard/carrier-bindings.xml). So around 10 aircraft will overwrite the new lighting binding anyway. err ... the tailwheel lock binding. (I didn't even know that it was there. I have that on my js.) We have still several keys globally unassigned, but it's increasingly hard to find one that isn't used by at least one aircraft. In the long run we'll have to reorganize a bit. We waste a lot of keys for obscure features that a typical simulator user will never need and/or that are too easy to press by accident (a/A, t/T, r, ...). The carrier bindings could IMHO be in a small popup dialog (like the ATC dialog). They aren't for controlling the aircraft after all, but to give orders to the carrier crew. m. Anyhow, I am not sure it would be a good idea to use the reserved carrier KEYS. There is only a the little number of persons who use and like the carriers, which is not the majority of the FG community :(, so i can understand that many persons don't mind about carrier, and i worry it. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). Please keep it. And I don't think a dialog would be a good way to fire the catapult. Regards 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] Minor keyboard reassignment
* Vivian Meazza -- Saturday 10 November 2007: Gerard robin wrote There is only a the little number of persons who use and like the carriers, I'm not even sure about that. It's one of the frequently asked questions, and it seems as if everyone of the IRC regulars uses the carrier once in a while. I do pretty often. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). And I don't think a dialog would be a good way to fire the catapult. Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) m. - 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] Minor keyboard reassignment
Melchior FRANZ Sent: 10 November 2007 10:00 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Minor keyboard reassignment * Vivian Meazza -- Saturday 10 November 2007: Gerard robin wrote There is only a the little number of persons who use and like the carriers, I'm not even sure about that. It's one of the frequently asked questions, and it seems as if everyone of the IRC regulars uses the carrier once in a while. I do pretty often. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). And I don't think a dialog would be a good way to fire the catapult. Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Sounds reasonable to me. V. - 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] Minor keyboard reassignment
Vivian Meazza a écrit : Melchior FRANZ Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Sounds reasonable to me. V. I Agree too. Alexis - 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] Minor keyboard reassignment
* alexis bory -- Saturday 10 November 2007: Vivian Meazza a écrit : Sounds reasonable to me. I Agree too. Umm ... it's only that I had forgotten that Ctrl-c is toggle clickable panel hotspots. So the plan doesn't work out exactly like that. m. - 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] Minor keyboard reassignment
On sam 10 novembre 2007, Melchior FRANZ wrote: * alexis bory -- Saturday 10 November 2007: Vivian Meazza a écrit : Sounds reasonable to me. I Agree too. Umm ... it's only that I had forgotten that Ctrl-c is toggle clickable panel hotspots. So the plan doesn't work out exactly like that. m. A stupid question: Why is it necessary to have a key for lights, isn't it a cockpit feature with hotspot, and switch ? 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] Minor keyboard reassignment
On Saturday 10 November 2007, gerard robin wrote: A stupid question: Why is it necessary to have a key for lights, isn't it a cockpit feature with hotspot, and switch ? I'm guessing because pressing a key on the keyboard resembles the gesture of pressing a key inside a cockpit of a real aircraft. -- Roy Vegard Ovesen - 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] Minor keyboard reassignment
On Sat, 10 Nov 2007, David Megginson wrote: So, in summary, I think a single switch to turn on all required interior and exterior lights for night flying can be a big win for FlightGear. That sounds reasonable. But maybe a menu entry or setup dialog would be better for this - after all it would usually only be used once per flight. Just my 0.05 SEK.. Cheers, Anders -- --- Anders Gidenstam mail: anders(at)gidenstam.org WWW: http://www.gidenstam.org/FlightGear/JSBSim-LTA/ - 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] Minor keyboard reassignment
On Sat, 10 Nov 2007 10:59:58 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) m. Im not sure what you mean by exaggerated , but its temporary anyway , until someone adds a sim/model/texture property , that is... If that gets implemented I'd like to add a livery dialogue to the help section , (without keypress to save keys ) , and I dont like the current popup dialog method ... we shouldn't need a separate folder just to enable livery changes thats MY 2 cents worth ;) Cheers -- SydSandy [EMAIL PROTECTED] - 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] Minor keyboard reassignment
David Megginson wrote: Switches are hard to find, especially (a) if you're not a real pilot, or (b) if you're not familiar with the aircraft. A single key to turn on all the lights can be very useful for a new user, or even for an experienced user who just wants to fly at night and doesn't know the aircraft or doesn't want to pan around the panel. snip So, in summary, I think a single switch to turn on all required interior and exterior lights for night flying can be a big win for FlightGear. Hi Dave, I just looked at the changes in cvs. There is a significant problem with at least this implementation of one key to turn on all the lights for all AC. There is no standard followed for how to implement nasal electrical systems. The patches you made to cvs will accomplish your stated goal for the pa24 and pa28, but not for the SenecaII or the dhc2. This is because when I wrote electrical.nas for the pa28, I started from the eleictrical.nas for the pa24. Some of the nasal electrical systems bypass switches all together and toggle properties such as /electrical/landinglights. Others include functional circuit breakers that would need to be verified. A second observation is that I virtually never turn on the white cabin light or the map light because I don't want to ruin my night vision. So even for the pa24, I would not want to have all the light on for most flights. For both the pa24 and the pa28, the keys assigned to toggle the switches are in the same order on the keyboard as in the AC. This was to make it easier to quickly turn on or off the switches you want w/o moving the mouse or view. Also, the Help Aircraft Help menu for the pa24 or pa28 gives complete switch info and starting procedure. What frustrates me with some AC is that I am left in the cockpit with no hot spots and also no help to allow me to find the magneto switch(es) or fuel valve. My vote would be to require either (1) hot start with engine running and all normal things turned on, or (2) a clearly written Help Aircraft Help that gets you started with what you need to be ready to take-off. Regards, Dave Perry - 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] Minor keyboard reassignment
On 10/11/2007, dave perry [EMAIL PROTECTED] wrote: I just looked at the changes in cvs. There is a significant problem with at least this implementation of one key to turn on all the lights for all AC. There is no standard followed for how to implement nasal electrical systems. The patches you made to cvs will accomplish your stated goal for the pa24 and pa28, but not for the SenecaII or the dhc2. This is because when I wrote electrical.nas for the pa28, I started from the eleictrical.nas for the pa24. Some of the nasal electrical systems bypass switches all together and toggle properties such as /electrical/landinglights. Others include functional circuit breakers that would need to be verified. This sounds like a pretty big problem beyond just my patch. Nasal has been great for letting people add functionality to FlightGear, but it causes a lot of problems for the property system, especially when people use different property names, override stuff, etc. It might be time for a refactoring pass through some of the models. A second observation is that I virtually never turn on the white cabin light or the map light because I don't want to ruin my night vision. So even for the pa24, I would not want to have all the light on for most flights. I know -- I don't turn them on either -- but I put them in just for completeness for now. I have no problem pulling them out, once we agree on a common subset (and fix some of the property inconsistencies). 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
[Flightgear-devel] Minor keyboard reassignment
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. 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] Minor keyboard reassignment
On sam 10 novembre 2007, David Megginson wrote: 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. All the best, David Hello David, The L is being used for Carrier look at the data/Input/Keyboard/carrier-bindings.xml file !-- map keys for launch-bar -- key n=76 nameL/name descLaunch-bar engage./desc binding commandproperty-assign/command property/controls/gear/launchbar/property value type=booltrue/value /binding mod-up binding commandproperty-assign/command property/controls/gear/launchbar/property value type=boolfalse/value /binding /mod-up /key We could have some conflict 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] Minor keyboard reassignment
On Fri, 9 Nov 2007 20:32:40 -0500 David Megginson [EMAIL PROTECTED] wrote: 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. All the best, David Hi David , I was using L for toggling through liveries ... any ideas on a common key for that ? -- SydSandy [EMAIL PROTECTED] - 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] Minor keyboard reassignment
* David Megginson -- Saturday 10 November 2007: 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). L is used to engage in the aircraft carrier's catapult (see $FG_ROOT/Input/Keyboard/carrier-bindings.xml). So around 10 aircraft will overwrite the new lighting binding anyway. Also see $FG_ROOT/Docs/keyboard/map.pdf for a quite up-to-date list of key assignments. m. - 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
