[Flightgear-devel] One down, two patches left
I give up; I withdraw the HUD patch. Too many people want the code to stay the same to make it a good basis for doing 3D cockpit work, even with the compatibility hook in place. (Although I suspect that if people tried it, they might change their minds). I'll maintain it for my personal use, of course. Folks can ask for it if they want it. Has anyone looked at the other two? One of them just makes three FDM values available from the property tree, is required for some cool stuff I've been doing with the Harrier, is harmless, and really shouldn't generate any objections at all. The other, which makes mouse clicks work in a 3D environment sounds like a win to me. I know for a fact that people have asked for it multiple times. Who hates this one? :) 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] One down, two patches left
Andy Ross wrote: I give up; I withdraw the HUD patch. Too many people want the code to stay the same to make it a good basis for doing 3D cockpit work, even Hmm, so far I've heard just two people who wants (just) the old HUD code, I for one would like to see the new code (also) included. with the compatibility hook in place. (Although I suspect that if people tried it, they might change their minds). I'll maintain it for my personal use, of course. Folks can ask for it if they want it. Has anyone looked at the other two? One of them just makes three FDM values available from the property tree, is required for some cool stuff I've been doing with the Harrier, is harmless, and really shouldn't generate any objections at all. The other, which makes mouse clicks work in a 3D environment sounds like a win to me. I know for a fact that people have asked for it multiple times. Who hates this one? :) I suspect they are on Davids back log of things wich should be commited some time ... Erik (But I might be wrong). ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] One down, two patches left
On Tue, 29 Oct 2002 19:26:57 +0100, Erik Hofman [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: Andy Ross wrote: I give up; I withdraw the HUD patch. Too many people want the code to stay the same to make it a good basis for doing 3D cockpit work, even Hmm, so far I've heard just two people who wants (just) the old HUD code, I for one would like to see the new code (also) included. ..leave it in as an option. with the compatibility hook in place. (Although I suspect that if people tried it, they might change their minds). I'll maintain it for my personal use, of course. Folks can ask for it if they want it. ..I like to see both HUD's available. My understanding is these two HUD concepts may be mutually exclusive to each other, so Andy's 3D HUD sits nicely on the front window, while Norman's 2D HUD follows the pilots eyes around. I can use both, each in different situations, one such may be model airplane HUD view. Has anyone looked at the other two? One of them just makes three FDM values available from the property tree, is required for some cool stuff I've been doing with the Harrier, is harmless, and really shouldn't generate any objections at all. The other, which makes mouse clicks work in a 3D environment sounds like a win to me. I know for a fact that people have asked for it multiple times. Who hates this one? :) I suspect they are on Davids back log of things wich should be commited some time ... Erik (But I might be wrong). ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
