You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As of now, once an instance of Engine has been created, all std::cout and std::cerr logs get forwarded into the Debug class, instead of the default stdout/stderr. Though it's useful, it removes the ability of users to debug log normally, especially in scenarios where the Editor isn't open, or the Debug panel is inaccessible, for example in a released game distribution.
Describe the solution you'd like Copystd::cout/std::cerr instead of simply forwarding, so that it is forwarded to both stdout/stderr (otherwise, the terminal window), while also being logged in the Debug class.
The text was updated successfully, but these errors were encountered:
Due to the one std::streambuf limit per std::ostream, logging has been split into two.
Printing to std::cout and std::cerr outputs to the default stdout (terminal), like normal.
Printing to engine.debug outputs to the Editor's built in Console.
Example usage:
engine.debug.err << "This is an error\n";
engine.debug.log << "This is a log\n";
Is your feature request related to a problem? Please describe.
As of now, once an instance of
Engine
has been created, allstd::cout
andstd::cerr
logs get forwarded into theDebug
class, instead of the defaultstdout
/stderr
. Though it's useful, it removes the ability of users to debug log normally, especially in scenarios where the Editor isn't open, or the Debug panel is inaccessible, for example in a released game distribution.Describe the solution you'd like
Copy
std::cout
/std::cerr
instead of simply forwarding, so that it is forwarded to bothstdout
/stderr
(otherwise, the terminal window), while also being logged in theDebug
class.The text was updated successfully, but these errors were encountered: