-
-
Notifications
You must be signed in to change notification settings - Fork 417
Description
Problem this feature should fix
The debug logging works fine if the game starts from a terminal, but for development with hot-reload on, clicking on the editor's start button is much more convenient.
The problem is that the editor's rendering freezes when it is not focused (which might be an intended behavior for saving computation). This causes the logging of the game cannot be displayed real-time in the editor's log tab, but we have to wait for the game to close.
Expected solution
I think a better solution is to pop up an extra os window for log displaying when the game starts from the editor, so that the editor can stay frozen and only render the logging window repeatedly. The logging window can also be resized to an arbitrary size for more convenient reading than the editor's current one. Additionally, the logging message from the engine and from the game logic should be separated, because there are a ton of info level loggings from the engine that may hide the user specified ones.