Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread Renk Thorsten
> Often airports are in or > near very scenery-intensive areas and reducing visibility can help a lot > in making the sim run usably for take-off, whereas once you're up and > away it's nice to be able to open the view back up again for > cross-country flying. This is applying a sledgehamm

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread Vivian Meazza
AJ wrote: > > On Mon, 04 Mar 2013 15:38:45 + > James Turner wrote: > > Aha, and instantly we get a usability discussion: > > > Right, you need the keys because you're working around a simulator bug > (frame-rate drops badly) using manual interaction. The correct fix isn't to > make the worka

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread Saikrishna Arcot
Just my 2 cents here. The primary reason I use the FoV/x binding is to see, read, and be able to use everything (or as much as I can) in my cockpit. Personally, I would rather scroll up/down, but that seems to have limits, as I can't zoom in as far as I want to by scrolling, but can using the k

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread AJ MacLeod
On Mon, 04 Mar 2013 15:38:45 + James Turner wrote: > Aha, and instantly we get a usability discussion: > Right, you need the keys because you're working around a simulator bug > (frame-rate drops badly) using manual interaction. The correct fix isn't to > make the workaround-UI easier, it's

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread Stefan Seifert
On Monday 04 March 2013 15:38:45 James Turner wrote: > You're the third person to say the same thing. But again, you don't actually > want to change the FoV at all. What you're doing (and everyone else) is > using this feature to look around 3D cockpits, right? In other word, our > cockpit navigat

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread James Turner
On 4 Mar 2013, at 14:54, AJ MacLeod wrote: Aha, and instantly we get a usability discussion: > Just sticking in my 2p worth... I would say I use z/Z almost every flight. > It can be useful for "cheating", as Thorsten said, but more usually as a > means of adjusting performance. Often airpo

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread AJ MacLeod
On Sun, 03 Mar 2013 11:24:29 + James Turner wrote: > What I'd like to see is the entire 'Ctrl' (Command on Mac) space reserved for > GUI functions, like a normal application - Ctrl-Q for quit, Ctrl-M for map > dialog, Ctrl-A for autopilot dialog, Ctrl-R for replay dialog (or radios > dialog

Re: [Flightgear-devel] Keyboard bindings

2013-03-04 Thread AJ MacLeod
On Sun, 03 Mar 2013 11:24:29 + James Turner wrote: > My *personal* feeling is that unless it's something the > 50% of users use > *each flight*, it shouldn't be a keybinding. So flaps, trim, CDI/HSI heading, > fine, but things to change view distance or FoV seem unnecessary to me. Just stic

Re: [Flightgear-devel] Key Bindings

2013-03-04 Thread Erik Hofman
The discussion reminded me of a blog post I once read: http://www.flightsim.com/vbfs/content.php?11603-Is-The-Default-Keyboard-Layout-Still-Relevant Might be worth reading, but also might be worth forgetting afterwards. Sometimes it's good to read someone else’s experience though. Erik -- htt

Re: [Flightgear-devel] Key Bindings

2013-03-04 Thread James Turner
On 4 Mar 2013, at 07:43, Vic Marriott wrote: > Hi James, > > Personally, I use 'ctrl' a lot when making my own shortcuts (outside FG). I'm > sure I can't be the only Mac user to do this. An example: If you were to > allocate 'ctrl+s' to a common FG function, using 'ctrl+s' sends my Mac to >