RE: [Flightgear-devel] Clickable panel and zooming
From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Curtis L. Olson So I would say go for it, people can always maintain their local overrides. It's not like we are changing any core functionality here. You will never get a consensus for anything you put before the list, but if you want to do anything really radical it might make sense to have a little discussion first. From a user's point of view, I am not against changing the default bindings, but would propose making them at once (maybe after discussion where required) and announcing all of them in a list. Given people are used to the present bindings and given they are in the cheat sheet (not sure anyone's using that...) I already see the posts like The s key does no longer work for me as announced, what shall I do. Besides: Wasn't someone working on a new GUI/menu system? Wouldn't it be a good idea to couple implementations of modified keys to that of the new GUI? Otherwise, I could imagine some better bindings and think it's a good idea to make a general revision of the historically developed bindings (the proposed change of x/X included). Given the new keys are readily accessible in keyboard.xml, I could try to catch up with a new cheat sheen then as soon as possible. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clickable panel and zooming
David Megginson wrote: To simplify things, I've just committed a base-package patch to bind zoom-in to '+', zoom-out to '-', and return to default zoom to '='. Ooh, this brings up a good point. Is there a place to store a default zoom, or are you just hardcoding the normal default? I have a button on my joystick mapped to mean recenter view. But the problem is that recentered means different things in different contexts. The A-4 needs to look down by 17 degrees, and I use a 65 degree FOV to keep the whole panel on the screen. The 172 is mostly straight ahead, as is the Harrier. It would be nice to store a per-aircraft (or per view?) default view configuration somewhere and have my button and the '=' key binding copy that onto the current view. Does a convention like this exist? Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clickable panel and zooming
David Megginson writes: Nice work on the clickable 2D/3D panel, Andy. A nice thing about the 3D panel is that you can zoom in on any instrument for detail work and then zoom out again -- this will be very valuable when we have more complicated GPS and flight director tools with lots of little text and buttons. To simplify things, I've just committed a base-package patch to bind zoom-in to '+', zoom-out to '-', and return to default zoom to '='. Now, if you want to adjust the altimeter, do this: 1. Switch to mouse view mode (right click twice), and use the mouse to centre the altimeter in the window. 2. Press '+' repeatedly to zoom in the panel. 3. Do your stuff. 4. Press '=' once to return to default zoom. When I have a chance, I might also bind the other mouse buttons to control zooming in view mode. David, Does it make sense to remove the 'x' and 'X' bindings and make them available for soemthing else? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clickable panel and zooming
Curtis L. Olson writes: Does it make sense to remove the 'x' and 'X' bindings and make them available for soemthing else? Yeah, but I don't want to get yelled at. It makes sense to change a lot of the keybindings, if people don't mind. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clickable panel and zooming
David Megginson writes: Curtis L. Olson writes: Does it make sense to remove the 'x' and 'X' bindings and make them available for soemthing else? Yeah, but I don't want to get yelled at. It makes sense to change a lot of the keybindings, if people don't mind. Well, the whole point of making the keyboard mapping xml configurable was to make these easy to change. a) for internationalization b) for people's different preference c) we could bind these same functions to other inputs or events. So I would say go for it, people can always maintain their local overrides. It's not like we are changing any core functionality here. You will never get a consensus for anything you put before the list, but if you want to do anything really radical it might make sense to have a little discussion first. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
