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. Ross NextBus 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
