Curtis L. Olson writes: > It sounds like you are bypassing SG_LOG() because it isn't doing what > you want. This seems like a bandaid solution at best. Perhaps we > should put these messages back in as SG_LOG( SG_ALERT ) and then > default 'release' builds to a minimum logging level of SG_ALERT rather > than collapsing SG_LOG into nothing as we do now.
That sounds reasonable. I wasn't sure what peoples' intentions were with SG_LOG, but it seemed like a bad idea to have situations where people might not get messages for catastrophic errors. What should we change to make SG_ALERT enabled by default? I haven't seen yet where that's happening (I configured with debug messages and still am not seeing any). All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
