On 09/11/2007, David Megginson <[EMAIL PROTECTED]> wrote:
> ... f 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.
There doesn't seem to be a consensus around the change, so I've
reverted keyboard.
* 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. An
* 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
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
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
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 i
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 th
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
> >> s
On Sun, 11 Nov 2007 11:06:42 +0100
Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * Syd&Sandy -- 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 ,
>
>
* 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 expose
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 valu
* 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 pr
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
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 t
* Syd&Sandy -- 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 acce
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
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
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
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
On 10/11/2007, gerard robin <[EMAIL PROTECTED]> wrote:
> A stupid question:
>
> Why is it necessary to have a key for lights, isn't it a cockpit feature with
> hotspot, and switch ?
Switches are hard to find, especially (a) if you're not a real pilot,
or (b) if you're not familiar with the aircra
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 a
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
* 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.
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
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 n
* 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 i
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:
> >
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 ..
* 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 wa
* 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/
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'
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
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 ar
33 matches
Mail list logo
