Re: [Flightgear-devel] Fwd: Re: preferences.xml change
On Thursday 12 December 2002 11:01 pm, Jim Wilson wrote: John Check [EMAIL PROTECTED] said: The main problem I have with our current views is that theres no random access, you have to cycle. If they were bound to specific key combos, I wouldn't have a problem. Maybe we can have distant and near views grouped? It wouldn't be a big change to make that possible (right now it isn't without a code change). Actually I was kind of thinking about binding V (shift v) so that it would always return to the view 0, the cockpit. That's usually the problem I run into...wanting to see if the animation is working and then finding my way back to the cockpit before stalling the aircraft. That's exactly the problem I have. I think what you propose is a nice compromise. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Fwd: Re: preferences.xml change
Michael would like to add an additional default view (a third, closer tower) to the base package preferences.xml. I'm against it since we offer the ability to add custom views and there's already too many default views for my taste. That's just my opinion and others will feel differently, so I thought I'd forward this discussion on to the list. Besides, I wouldn't want to get on Michael's bad side over this :-) Best, Jim Forwarded From: Michael Selig [EMAIL PROTECTED] Hi Jim, Ok, I see the thread now. In this case, I would opt for adding a 6th view to include the lookat tower view close to the airplane. I think the average user would find this more interesting (e.g. watching the 747 take off this way is pretty cool). For developing flight models, I find it really handy because I am close to the airplane and viewing in an air show mode. I think most commercial sims have many view options that don't require the user to tweak config files. (FWIW I have 6 other sims here at home.) So I think adding a 6th view is not too crazy, especially one that a lot of users would put on their nice to have list. BTW - I did not know that w/ the fixed view mousing around worked. That's cool and should be kept in there. Hence, my proposal --- + one more view. Regards, Michael At 12/12/02, you wrote: Michael Selig [EMAIL PROTECTED] said: Should I recommit this change, which perhaps was inadvertently tweaked back to the fixed view looking off in the distance (w/o the airplane in view at KSFO)? Hi Michael, Actually I did look at that view. It was a variation on the lookat tower raised up and closer to the plane. In regards to the multiple aircraft thing, I was refering to David Luff's message saying that he used the 4th view quite extensively: http://seneca.me.umn.edu/pipermail/flightgear-devel/2002-November/013136.html The gist of it is, I don't think we need another default view and if the 4th view was to be removed it should be to reduce the number total views. The 4th view is the only view mode that would aid someone working on what David is doing, and it seems that for now that is reason enough to leave it in. If you feel strongly otherwise, I'm cool with bringing this to the list (that was my original point about discussing changes in prefrences.xml ;-) ). Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Re: preferences.xml change
Jim Wilson wrote: Michael would like to add an additional default view (a third, closer tower) to the base package preferences.xml. I'm against it since we offer the ability to add custom views and there's already too many default views for my taste. I'd argue that this is a UI limitation. Having a fixed set of views works fine for N=3 or so, but forcing the user to cycle through 6 is just too much. Even explaining the difference between some of them is a chore. Why not add an extra menu where the user can select from a list, instead? Then the v key can toggle between cockpit mode (by convention always view 0) and whatever the last selection was (the default could be external view, currently view 1). This should remain easy to use up to N=10 or so. 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] Fwd: Re: preferences.xml change
At 12/12/02, Andy Ross wrote: Jim Wilson wrote: Michael would like to add an additional default view (a third, closer tower) to the base package preferences.xml. I'm against it since we offer the ability to add custom views and there's already too many default views for my taste. I'd argue that this is a UI limitation. Having a fixed set of views works fine for N=3 or so, but forcing the user to cycle through 6 is just too much. Even explaining the difference between some of them is a chore. Why not add an extra menu where the user can select from a list, instead? Then the v key can toggle between cockpit mode (by convention always view 0) and whatever the last selection was (the default could be external view, currently view 1). This should remain easy to use up to N=10 or so. UI limitation is what? I don't think you mean Univ of Illinois! User Interface? We're talking hear about a feature. I think it's pretty clear what I am after (but it got cropped out). The view being discussed is one that sits about 200 ft high near the aircraft at KSFO. It looks down on the airplane on the runway and then follows it along. It's a great view. You sit there watching effectively an airshow. If this 6th view could be integrated into a menu thing, GREAT. I think we need more stuff in GUI format, but having developed a lot of code ... it is a lot easier to develop w/ config files and stop there leaving the GUI part for later (which often equates to never). The idea of toggling back and forth between two views (some default and last GUI selected view) sounds really good. Whatever happens w/ this thread, let's not take out views from the current set of five! I don't like making a practice of shooting myself in the foot. :) Regards, Michael ** Prof. Michael S. Selig Dept. of Aero/Astro Engineering University of Illinois at Urbana-Champaign 306 Talbot Laboratory 104 South Wright Street Urbana, IL 61801-2935 (217) 244-5757 (o), (509) 691-1373 (fax) mailto:[EMAIL PROTECTED] http://www.uiuc.edu/ph/www/m-selig http://www.uiuc.edu/ph/www/m-selig/faq.html (FAQ) ** ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Re: preferences.xml change
On Thursday 12 December 2002 6:06 pm, Jim Wilson wrote: Michael would like to add an additional default view (a third, closer tower) to the base package preferences.xml. I'm against it since we offer the ability to add custom views and there's already too many default views for my taste. That's just my opinion and others will feel differently, so I thought I'd forward this discussion on to the list. Besides, I wouldn't want to get on Michael's bad side over this :-) The main problem I have with our current views is that theres no random access, you have to cycle. If they were bound to specific key combos, I wouldn't have a problem. Maybe we can have distant and near views grouped? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Re: preferences.xml change
John Check [EMAIL PROTECTED] said: The main problem I have with our current views is that theres no random access, you have to cycle. If they were bound to specific key combos, I wouldn't have a problem. Maybe we can have distant and near views grouped? It wouldn't be a big change to make that possible (right now it isn't without a code change). Actually I was kind of thinking about binding V (shift v) so that it would always return to the view 0, the cockpit. That's usually the problem I run into...wanting to see if the animation is working and then finding my way back to the cockpit before stalling the aircraft. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
