=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-16_06:30:33 (mfranz) /var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx
- complain about attempts to attach a listener to a tied node - do *not* complain about a listener writing to its own node, but don't enter recursion either =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-16_06:48:22 (mfranz) /var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx ... but then again: it's only a rumor that listeners on tied properties don't work. And like most rumors, it's untrue. So just output a debug message. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-17_12:58:53 (ehofman) /var/cvs/FlightGear-0.9/source/configure.ac /var/cvs/FlightGear-0.9/source/src/Cockpit/cockpit.cxx /var/cvs/FlightGear-0.9/source/src/Cockpit/hud_ladr.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_ladder.cxx /var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx Use one standard define for enableing of the Special Purpose FDM code. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-17_13:14:31 (mfranz) /var/cvs/FlightGear-0.9/source/src/Systems/pitot.cxx /var/cvs/FlightGear-0.9/source/src/Systems/pitot.hxx only consider positive airspeed in longitudinal axis =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-17_15:22:45 (ehofman) /var/cvs/FlightGear-0.9/source/configure.ac Somehow this test stopped working on my PC. At least the new solution should work for ages. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-18_16:35:11 (curt) /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx - Code cleanups. - Fix a warning about class member initialization order. - Clear up a problem with the default autopilot behavior on the back side of an ILS in preparation for adding a real "back course" approach mode. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-19_14:46:53 (andy) /var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx /var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.hxx Rework the naModLock()/naModUnlock() semantics to be more maintainable. The rules are simple (extension functions are called *with* the lock, which must be dropped before calling naCall(), which grabs it) but the tracking of when the lock was held was getting a little confused. Keep a "nasal call depth" count in the subsystem to figure out whether we are making a sub-call and thus hold the lock. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-19_22:43:07 (curt) /var/cvs/FlightGear-0.9/source/src/Main/main.cxx Always check for if glPointParameterIsSupported, even if we haven't asked for point light distance attenuation, because we may want to toggle this on via the rendering options gui. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-19_22:47:39 (curt) /var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx Add a configuration property to turn on/off the use of point sprites. Generally you want point sprites for performance reasons when enhanced runway lighting (and smooth points) are activated. Most hardware doesn't accelerate the rendering of standard smooth points, so without point sprites you will kill your night time performance if you turn on enhanced runway lighting. Note that enhanced runway lighting "breaks" our clever scheme to make the runway lighting brightness vary with the relative view angle. This means with enhanced lighting on, all lights are equally bright no matter what direction you view them from. So perpendicular runways are just as bright as runways you are directly lined up with (when enhanced runway lighthing is activated.) You can revert to the original lighting scheme by turning off enhance runway lights, turning off distance-attenuation, and turning off point-sprites in the rendering options menu. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-21_10:48:57 (curt) /var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx Small tweaks to point lighting configuration to better control the appearance of approach rabbits. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-21_14:37:04 (curt) /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.hxx Add support for a back-course mode. Nothing changes visualy, but this reverses the autopilot helpers so that the FD/AP can properly fly a BC appr. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-22_03:00:56 (mfranz) /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_instrument.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_misc.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/Makefile.am add MIL-STD-1787B Aiming Reticle (stadiametric; TODO: standby) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-22_03:49:47 (fredb) /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_misc.cxx Win32 fix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-22_05:09:36 (mfranz) /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.hxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_gauge.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_instrument.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_ladder.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_misc.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_runway.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_tape.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_tbi.cxx get rid of struct Point and get_centroid(). Instruments may access *their* properties directly. This is properly encapsulated already. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-22_06:48:22 (mfranz) /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.cxx /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_runway.cxx don't be afraid of the comma operator! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2006-07-22_12:27:43 (mfranz) /var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_misc.cxx reticle should fit into bounding box (don't take diameter as radius) 2f585eeea02e2c79d7b1d8c4963bae2d ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
