* [EMAIL PROTECTED] (Jon S Berndt) [2002.10.24 12:08]: > On Thu, 24 Oct 2002 09:30:29 -0700 > Andy Ross <[EMAIL PROTECTED]> wrote: > >Richard Bytheway wrote: > >>We really ought to sort out the ability to disable *any* > >>console > >>output after initialisation on Windows... > > > >Is it maybe time to revisit the priority of most of the log messages? > >I mean, the vast majority of these things are debugging output for > >code that is mature and stable. Even most developers > >don't care about tile cache behavior anymore. > > I agree with this. At the least, we ought to have > different levels of output for the released binaries on > the web site - those who download the binaries are (I > would think) users who could care less about the console > output - and indeed might find it confusing. The default > there should be for less console output. Also, I feel that > some things such as the solution and landing reports are > generally useful and of interest, but perhaps they could > be made optional as well. For instance the user, after > landing, requests a landing report from a "Reports" menu. > The information can be passed up into FlightGear easily > enough from JSBSim, at least.
I mentioned in another thread that I thought the log levels where configurable at runtime, and I've confirmed that they are. The property is /sim/logging/priority. It defaults to "info", but you can change it to "warn" or "alert" to quell the verbose logging. We might want to set the log level to "warn" in the base package when we make a public release. Beyond that, I agree with Andy. There are a lot of messages that just don't seem like useful "info" to most of us, but fall more under the "debug" umbrella. We hardly use the "bulk" priority; maybe we can move the "debug" messages to "bulk" and move some of the "info" messages down to "debug". And when I say "we", I mean "someone else." :-) -- Cameron Moore [ If God was a perl hacker: ($child = 'grave') =~ s/v/c/; ] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
