Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

On 27/09/10 22:11, willie wrote: > btw the help option (?) on the Command Mode Dialog doesn't work for me, > can anyone else confirm? It works OK - it just sends the help message to the console, which is not much use in full-screen mode. Willie --

Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

Willie wrote: > > On 27/09/10 21:29, Stuart Buchanan wrote: > > Hi All, > > > > Currently there are a number of key bindings to enable various > > auto-pilot modes, e.g.: > > > > Ctrl-A Altitude lock > > Ctrl-H Heading lock > > Ctrl-G Glideslope lock > > Ctrl-N NAV1 lock > > Ctrl-P Pitch hold > >

Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

On 27/09/10 21:29, Stuart Buchanan wrote: > Hi All, > > Currently there are a number of key bindings to enable various > auto-pilot modes, e.g.: > > Ctrl-A Altitude lock > Ctrl-H Heading lock > Ctrl-G Glideslope lock > Ctrl-N NAV1 lock > Ctrl-P Pitch hold > Ctrl-S Autothrottle > Ctrl-T Terrain lock

[Flightgear-devel] Autopilot key bindings and the problem of backspace

Hi All, Currently there are a number of key bindings to enable various auto-pilot modes, e.g.: Ctrl-A Altitude lock Ctrl-H Heading lock Ctrl-G Glideslope lock Ctrl-N NAV1 lock Ctrl-P Pitch hold Ctrl-S Autothrottle Ctrl-T Terrain lock Ctrl-W Wing level F6 - Heading lock Unfortunately, it is all t