Erik wrote:
> FlightGear should always display messages when it is labeled "alert".
> Maybe there is a log-level mismatch between FlightGear and JSBSim?
Here's the controlling code in JSBSim.cxx:
switch (logbuf::get_log_priority()) {
case SG_BULK:
FGJSBBase::debug_lvl = 0x1f;
break;
case SG_DEBUG:
FGJSBBase::debug_lvl = 0x0f;
case SG_INFO:
FGJSBBase::debug_lvl = 0x01;
break;
case SG_WARN:
case SG_ALERT:
FGJSBBase::debug_lvl = 0x00;
break;
}
If the JSBSim variable, debug_lvl, is set to zero, nothing comes out of
JSBSim. That turns off JSBSim output. Setting debug_lvl to 1 echoes the
inputs that JSBSim gets. Anything above that adds more stuff - probably more
than FlightGear needs. An overhaul is probably in order on the JSBSim side,
but at the moment at least the WARN|ALERT level of SimGear should set
debug_lvl to 0x01.
Jon
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
