=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_07:26:35 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/util.cxx
/var/cvs/FlightGear-0.9/source/src/Main/util.hxx

add unescape function for conversion of \t, \n, \x1b etc. in <format> strings


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_08:59:01 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Network/generic.cxx
/var/cvs/FlightGear-0.9/source/src/Network/generic.hxx

generic/output:
- support optional <preamble> and <postamble> which are written right
  after opening and before closing respectively. This can be used for a header
  line or an XML header.
- unescape <preamble>, <postamble>, <format>, <line_separator>, <var_separator>
  so that \t, \n, \r, \f, \v, \xnn, \nnn can be used directly (\a and \b are
  ignored; use \\ for the backslash) The long names ("carriagereturn") are still
  supported for <var_separator>, but one can just use \r, or \r\n too.
- don't abort when a chunk doesn't have a <node>. This is useful for adding
  constant chunks which consist only of a <format>, such as XML tags.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_12:15:56 (mfranz)
/var/cvs/FlightGear-0.9/source/docs-mini/README.IO

corrections, extensions, spelling, cleanup


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_12:15:57 (mfranz)
/var/cvs/FlightGear-0.9/source/docs-mini/README.protocol

corrections, extensions, spelling, cleanup


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_12:36:32 (mfranz)
/var/cvs/FlightGear-0.9/source/src/FDM/UFO.cxx
/var/cvs/FlightGear-0.9/source/src/FDM/UFO.hxx

cleanup: extract globals->get_controls()


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_13:32:31 (mfranz)
/var/cvs/FlightGear-0.9/source/docs-mini/README.protocol

improve XML example


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-29_17:17:38 (mfranz)
/var/cvs/FlightGear-0.9/source/docs-mini/README.protocol

use correct example output


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-07-31_10:51:17 (andy)
/var/cvs/FlightGear-0.9/source/src/FDM/YASim/Rotorpart.cpp

Maik: Use exact calculation instead of 1st order approximation


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-08-03_07:06:22 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Environment/environment_ctrl.cxx
/var/cvs/FlightGear-0.9/source/src/Environment/environment_ctrl.hxx

Stuart BUCHANAN:

"interpolates METAR changes over time as follows:
1) Wind changes are interpolated as vectors, so the change is much more
natural than before - no-longer will your aircraft be suddenly shoved to
one side.
2) Visibility is interpolated as an X-value, which looks pretty neat.
3) Cloud heights and thicknesses are interpolated if they are close to the
aircraft. Cloud textures are not."


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-08-03_13:02:30 (mfranz)
/var/cvs/FlightGear-0.9/source/src/AIModel/AIManager.cxx
/var/cvs/FlightGear-0.9/source/src/AIModel/AIManager.hxx

prevent multiple loading of one and the same scenario


2f585eeea02e2c79d7b1d8c4963bae2d

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to