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

In game logs #738

Open
davesmith00000 opened this issue May 11, 2024 · 1 comment
Open

In game logs #738

davesmith00000 opened this issue May 11, 2024 · 1 comment
Labels
good first issue Good for newcomers help welcome Extra attention is needed

Comments

@davesmith00000
Copy link
Member

At the moment all logs are piped to the console, which is ok, but if you aren't looking for them then you might not see them. Might be good to revisit the IndigoLogger and have it render to an in game console log that pops up on error.

Will need a way to close the logs, and a way to disable them completely "in production". Or at least, make them not appear on certain error levels.

@davesmith00000 davesmith00000 added help welcome Extra attention is needed good first issue Good for newcomers and removed good first issue Good for newcomers labels May 11, 2024
@davesmith00000
Copy link
Member Author

I've dithered on whether or not this is a good first issue. I think it could be depending on the solution.

Two approaches:

  1. It's some sort of deep integration with the engine: This is not beginner friendly. :)
  2. We do it like the FPS Counter and make it a SubSystem that users can optionally add.

The subsystem version is very doable and I think I like it better, because it also means the "in production" requirement is just up to the user to manage with a flag or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help welcome Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant