Currently we do not have any logging set up, and due to the nature of how we are manipulating the terminal screen we do not always see expected error output.
Logging to file should be added with a boolean flag set up to toggle it. It the initial point of setup if it can log runtime panics that would be a good start. Individual error logging points (and probably some supporting functions) can be added later.
Currently we do not have any logging set up, and due to the nature of how we are manipulating the terminal screen we do not always see expected error output.
Logging to file should be added with a boolean flag set up to toggle it. It the initial point of setup if it can log runtime panics that would be a good start. Individual error logging points (and probably some supporting functions) can be added later.
Since this issue was posted we have not moved forward with a developer mode or any logging. We have made it so that if there is a panic, we can see it. So that is an improvement.
Since this issue was posted we have not moved forward with a developer mode or any logging. We have made it so that if there is a panic, we can see it. So that is an improvement.
Currently we do not have any logging set up, and due to the nature of how we are manipulating the terminal screen we do not always see expected error output.
Logging to file should be added with a boolean flag set up to toggle it. It the initial point of setup if it can log runtime panics that would be a good start. Individual error logging points (and probably some supporting functions) can be added later.
Since this issue was posted we have not moved forward with a developer mode or any logging. We have made it so that if there is a panic, we can see it. So that is an improvement.