Re: [Flightgear-devel] Broken Code

2002-02-27 Thread D Luff
David Megginson writes: There are two important C++ APIs you have to learn for properties -- I added extensive documentation comments to both so that contributors won't have to guess how to use them. The low-level implementation is declared in simgear/misc/props.hxx, and Curt has

re: [Flightgear-devel] Broken Code

2002-02-26 Thread David Megginson
John Wojnaroski writes: On Jan 19 the FGEngInterface and FGGearInterface were removed from the flight.hxx source. It broke a lot of code in the opengc interface as well as internal logic to modulate the display symbols. Is the OpenGC interface in the FlightGear code base, or separate?

Re: [Flightgear-devel] Broken Code

2002-02-26 Thread David Megginson
John Wojnaroski writes: Excuse me, but if you go back you will see that I allowed to the fact that I was unclear on the idea of the properties, but was willing to give it a go. I cannot find that message or my replies to it through Google, but it may have missed indexing some archived

Re: [Flightgear-devel] Broken Code

2002-02-26 Thread Jim Wilson
John Wojnaroski [EMAIL PROTECTED] said: Excuse me, but if you go back you will see that I allowed to the fact that I was unclear on the idea of the properties, but was willing to give it a go. If this is truely an open source project then other ideas and opinions need to be honored, not

[Flightgear-devel] Broken Code

2002-02-25 Thread John Wojnaroski
Hi, On Jan 19 the FGEngInterface and FGGearInterface were removed from the flight.hxx source. It broke a lot of code in the opengc interface as well as internal logic to modulate the display symbols. I have made requests to this group for help in fixing what was broken by this change. I don't