From: Curtis L. O. <cu...@fl...> - 2006-06-22 18:54:22
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-15_14:16:21 (frohlich) /var/cvs/FlightGear-0.9/source/src/AIModel/AIAircraft.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/adf.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/adf.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/dme.cxx Make more use of SGGeod =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-15_14:16:22 (frohlich) /var/cvs/FlightGear-0.9/source/src/Instrumentation/dme.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/kr_87.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/kr_87.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/marker_beacon.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/tacan.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/tacan.hxx /var/cvs/FlightGear-0.9/source/src/Navaids/navlist.cxx /var/cvs/FlightGear-0.9/source/src/Navaids/navlist.hxx /var/cvs/FlightGear-0.9/source/src/Navaids/navrecord.hxx Make more use of SGGeod =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_04:31:34 (mfranz) /var/cvs/FlightGear-0.9/source/src/Cockpit/Makefile.am /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.hxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_card.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_gaug.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_ladr.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_opts.hxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_scal.cxx - move FloatToInt() function to simgear/math/fastmath.hxx, renamed to float_to_int() for consistency reasons - remove hud_opts.hxx =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_05:17:06 (fredb) /var/cvs/FlightGear-0.9/source/src/AIModel/AIFlightPlan.cxx /var/cvs/FlightGear-0.9/source/src/ATC/ATCProjection.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_labl.cxx /var/cvs/FlightGear-0.9/source/src/Systems/electrical.cxx /var/cvs/FlightGear-0.9/source/src/Systems/vacuum.cxx Compile again on Win32 platforms =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_09:22:21 (curt) /var/cvs/FlightGear-0.9/source/src/AIModel/AIAircraft.cxx This patch only affects aircraft (AI Models) that have no predefined flightplan. Such aircraft are given some initial conditions that they fly with. They proceed on in "freeflight" mode indefinitely. For example, there is a refueling demo where the tanker starts at 3000', 280 kts, and in a 15 degree bank, and then continues to orbit indefinitely. For these aircraft with no flightplan, I have added several control nodes in controls/flight that allow a script or menu or external application to set heading, altitude, bank angle, and speed. This permits some level of interactive or scripted control over AI aircraft. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_09:22:22 (curt) /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.cxx This patch only affects aircraft (AI Models) that have no predefined flightplan. Such aircraft are given some initial conditions that they fly with. They proceed on in "freeflight" mode indefinitely. For example, there is a refueling demo where the tanker starts at 3000', 280 kts, and in a 15 degree bank, and then continues to orbit indefinitely. For these aircraft with no flightplan, I have added several control nodes in controls/flight that allow a script or menu or external application to set heading, altitude, bank angle, and speed. This permits some level of interactive or scripted control over AI aircraft. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_14:10:20 (curt) /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.cxx Add a flag that allows the simulator to force "radar" computations even if AI aircraft are out of range or the piloted aircraft has no radar system. These computation include range, bearing, and angular offset relative to the piloted aircraft. This gives some external script the control the behavior of the AI aircraft relative to the piloted aircraft without requiring a radar system, and without requiring the AI aircraft to be within radar range. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-16_14:29:34 (mfranz) /var/cvs/FlightGear-0.9/source/src/Cockpit/Makefile.am /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.hxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_lat.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_lon.cxx - remove unused classes lat_label and lon_label (it's the instr_label that makes the lon/lat labels) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_11:33:00 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/fg_props.cxx move generation of lon/lat string representations here from cockpit.cxx. Thanks to tied functions, this is only executed when the node is read. This will be done by the old & new HUD code, the latter of which won't have a special lon/lat mode at all. Instead it will be regular labels that point to these properties for displaying lon/lat. I would have liked to avoid the duplication of code (lon and lat being basically the same thing), and to avoid using static buffers and all, but ... if anyone wants to make it prettier, go ahead. The format is controlled by /sim/lon-lat-format (will be changed if I find a better place). =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_11:37:33 (mfranz) /var/cvs/FlightGear-0.9/source/src/GUI/gui_funcs.cxx /var/cvs/FlightGear-0.9/source/src/GUI/menubar.cxx remove obsolete "lon/lat format" commands that have been labeled "deprecated" and "will very soon be removed" since years =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_11:40:51 (mfranz) /var/cvs/FlightGear-0.9/source/src/Cockpit/cockpit.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.hxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_labl.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_rwy.cxx remove lon/lat string representation generating functions; this is now done in Main/fg_props.cxx and available via /position/{long,lat}itude-string =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_13:08:53 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/fg_props.cxx - add direction letter to numeric mode, too - avoid negative sign on 0.00 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_13:25:12 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/fg_props.cxx getGMTstring: remove leading space, cleanup =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-17_14:09:38 (mfranz) /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.cxx set blend mode back to make 2D panels opaque when used with transparent HUDs =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-19_05:00:25 (mfranz) /var/cvs/FlightGear-0.9/source/src/Instrumentation/tacan.cxx Vivian MEAZZA: "Bugfix - a fix to fix the hack which hacked the TACAN Channel/freq pairing." =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-21_04:36:15 (mfranz) /var/cvs/FlightGear-0.9/source/src/Include/Makefile.am /var/cvs/FlightGear-0.9/source/src/Include/auto_ptr.hxx /var/cvs/FlightGear-0.9/source/src/Include/fg_stl_config.h - auto_ptr.hxx: not used anywhere; functionally replaced by simgear/structure/SGSharedPtr.hxx - fg_stl_config.h: only used by obsolete auto_ptr.hxx =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-21_14:53:47 (mfranz) /var/cvs/FlightGear-0.9/source/src/GUI/new_gui.cxx umm ... fix a tiny leak :-) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-21_16:17:21 (mfranz) /var/cvs/FlightGear-0.9/source/src/GUI/new_gui.cxx oh, and by the way: this destructor didn't do anything useful :-) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-21_16:23:20 (curt) /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx Existing ground track estimation code depended on current_value - last_value each frame. However, often these values didn't change leading to bogus data getting introduced into the computational pipeline. This patch switches to a much more sane method for ground track computation. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-06-22_03:35:50 (mfranz) /var/cvs/FlightGear-0.9/source/src/GUI/new_gui.hxx ok, so the old ~FGFontCache() was useless. But at least it didn't call the buggy ~fnt(), causing an abort() ... ;-) (Only loaded texture fonts (*.txf) have a new'ed puFont. The built-in pixmap fonts don't, and may, thus, not be deleted.) 2f585eeea02e2c79d7b1d8c4963bae2d |