Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support SimGear logging #578

Open
legoboyvdlp opened this issue Jan 30, 2022 · 1 comment
Open

Support SimGear logging #578

legoboyvdlp opened this issue Jan 30, 2022 · 1 comment

Comments

@legoboyvdlp
Copy link
Contributor

When JSBSim is used with FlightGear, the std::cout / std::cerr messages are printed to the console. FlightGear closes so quickly, that it is impossible to read the error messages.

If JSBSim would use the SimGear logging mechanism, this would allow the error message to be routed to fgfs.log, so that the developer can read the message. Otherwise, the error message is not useful, because it is not possible to read it before FlightGear -- and the console -- close down.

As requested on sourceforge ticket.

@bcoconni
Copy link
Member

Thanks for the feature request @legoboyvdlp. I guess indeed JSBSim could make use of SG_LOG to redirect the messages to various locations (console, log file, etc.).

We need to see how fonts decorations (colors, bold, etc.) are managed since they are using control characters which will look ugly on a log file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants