Debugger engine component

[TheRealKaup]

• File logging (optionally rotatable), user sets a file to log to and logs get written there.
• Terminal logging, prints rotating logs to the lines that come after IO's image, makes sure those aren't erased and are visible without flickering. Perhaps can also be scrolled with special keys.
• Log content:
  • Log index
  • Type, can be filtered (operating - text describes what will happen next / info - text describes a certain piece of information / warning - text describes something that should not happen, such as user accessing an empty memory container)
  • Severity, can be filtered
  • Time
  • Calling structure's info (name, shortened address)
  • Text
  • Unique color for each structure (if in terminal)

[TheRealKaup]

There isn't any large program made with KTech that could benefit from these features, which is why they sound irrelevant or excessive. Debugging the engine using logs made by the engine itself, is, according to my experience doing so, not as easy and helpful as instead simply building with debug symbols and breaking with GDB; this proposed Debugger engine component is indeed for games made with KTech rather than KTech itself.